Notices


Reply
Thread Tools
Posts: 111 | Thanked: 9 times | Joined on May 2010
#301
Originally Posted by mattiasbäx View Post
How stupid! But yet it worked

Now when trying to purge QSpot and Libopenspotify it seems like the purge goes through, though it says E: Sub-process /usr/bin/dpkg returned an error code (1)
After doing the cache clean and installing Qspot it also says E: Sub-process /usr/bin/dpkg returned an error code (1). When starting the newly installed QSpot i still get the library is too old error at log in screen.
 
Posts: 564 | Thanked: 693 times | Joined on Apr 2010
#302
Indeed very strange, as it should indeed work. Do you have any possibility to try with another client (e.g., yaspot or footify) and see if you are able to login with any of them?

Originally Posted by mattiasbäx View Post
After doing the cache clean and installing Qspot it also says E: Sub-process /usr/bin/dpkg returned an error code (1). When starting the newly installed QSpot i still get the library is too old error at log in screen.
 
Posts: 111 | Thanked: 9 times | Joined on May 2010
#303
Originally Posted by aenbacka View Post
Indeed very strange, as it should indeed work. Do you have any possibility to try with another client (e.g., yaspot or footify) and see if you are able to login with any of them?
Yaspot works atleast.

Last edited by mattiasbäx; 2010-10-08 at 06:59.
 
mece's Avatar
Posts: 1,111 | Thanked: 1,985 times | Joined on Aug 2009 @ Åbo, Finland
#304
Originally Posted by mattiasbäx View Post
After doing the cache clean and installing Qspot it also says E: Sub-process /usr/bin/dpkg returned an error code (1). When starting the newly installed QSpot i still get the library is too old error at log in screen.
That means something is wrong and the some packages were left unconfigured. You need to give the whole output, otherwise we can't know what the problem is.

(E: The commands I gave should execute without errors for everything to work. My guess is that there is some other broken package that stops apt from getting its work done)
__________________
Class .. : Meddler, Thread watcher, Developer, Helper
Humor .. : [********--] Alignment: Pacifist
Patience : [*****-----] Weapon(s): N900, N950, Metal music
Agro ... : [----------] Relic(s) : N95, NGage, Tamyia Wild One

Try Tweed Suit for your hardcore twittering needs
http://twitter.com/mece66
I like my coffee black, like my metal.

Last edited by mece; 2010-10-08 at 07:02.
 
Posts: 111 | Thanked: 9 times | Joined on May 2010
#305
Originally Posted by mece View Post
That means something is wrong and the some packages were left unconfigured. You need to give the whole output, otherwise we can't know what the problem is.

(E: The commands I gave should execute without errors for everything to work. My guess is that there is some other broken package that stops apt from getting its work done)
apt-get remove --purge qspot libopenspotify gives

Reading package lists... Done
Building dependecy tree
Reading state information... Done
The folling packages will be REMOVED:
libopenspotify* qspot*
0 upgraded, 0 newly installed, 2 to remove and 12 not upgraded
2 not fully installed or removed
after this operation, 713kb disk space will be freed.
Do you want to continue [Y/n]?
*i put in J for yes*
(Reading database ... 35720 files and directories currently installed.)
Removing qspot ...
Removing libopenspotify ...
Setting up accont-plugin-salut (0.10) ...
/var/lib/dpkg/info/account-plugin-salut.postinst: line 6: /etc/init.d/avahi-daemon: not found
dpkg: error processing account-plugin-salut (--configure):
subprocess post-installation script returned error exit status 127
dpkg: dependency problems prevent configuration to telepathy-extras:
telepathy-extras depends on account-plugin-salut; however:
Package account-plugin-salut is not configured yet.
dpkg: error processing telepathy-extras (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
account-plugin-salut
telepathy-extras
E: Sub-process /usr/bin/dpkg/ returned an error code (1)

That's the whole thing when I do the purge of qspot and libopenspotify, but it is still uninstalled it seems.
 
Posts: 564 | Thanked: 693 times | Joined on Apr 2010
#306
I also myself just tried a complete purge / reinstall of qspot and it still works ok. Do you get some other error message if you e.g., try to supply invalid username / password when trying to login with qspot?

Originally Posted by mattiasbäx View Post
apt-get remove --purge qspot libopenspotify gives

Reading package lists... Done
Building dependecy tree
Reading state information... Done
The folling packages will be REMOVED:
libopenspotify* qspot*
0 upgraded, 0 newly installed, 2 to remove and 12 not upgraded
2 not fully installed or removed
after this operation, 713kb disk space will be freed.
Do you want to continue [Y/n]?
*i put in J for yes*
(Reading database ... 35720 files and directories currently installed.)
Removing qspot ...
Removing libopenspotify ...
Setting up accont-plugin-salut (0.10) ...
/var/lib/dpkg/info/account-plugin-salut.postinst: line 6: /etc/init.d/avahi-daemon: not found
dpkg: error processing account-plugin-salut (--configure):
subprocess post-installation script returned error exit status 127
dpkg: dependency problems prevent configuration to telepathy-extras:
telepathy-extras depends on account-plugin-salut; however:
Package account-plugin-salut is not configured yet.
dpkg: error processing telepathy-extras (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
account-plugin-salut
telepathy-extras
E: Sub-process /usr/bin/dpkg/ returned an error code (1)

That's the whole thing when I do the purge of qspot and libopenspotify, but it is still uninstalled it seems.
 
Posts: 111 | Thanked: 9 times | Joined on May 2010
#307
Originally Posted by aenbacka View Post
I also myself just tried a complete purge / reinstall of qspot and it still works ok. Do you get some other error message if you e.g., try to supply invalid username / password when trying to login with qspot?
It seems if I change just a few letters in the login name it doesn't say so, but if i put in asdfadfgadfliahliha or something simular it says wrong username and/or password.
 
Posts: 564 | Thanked: 693 times | Joined on Apr 2010
#308
It indeed seems like some check fails at the Spotify backend, due to the library reporting too old revision. It would be interesting to know if someone else also experience this problem.

Originally Posted by mattiasbäx View Post
It seems if I change just a few letters in the login name it doesn't say so, but if i put in asdfadfgadfliahliha or something simular it says wrong username and/or password.
 
Posts: 564 | Thanked: 693 times | Joined on Apr 2010
#309
Just a quick question; has anyone else started receiving
'client too old..' message when trying to login using QSpot?
 
Posts: 4 | Thanked: 2 times | Joined on Jun 2010 @ Finland
#310
Works OK for me.
 

The Following User Says Thank You to fixie For This Useful Post:
Reply

Tags
premium account, spotify


 
Forum Jump


All times are GMT. The time now is 02:49.