Active Topics
-
Porting apps to Leste (29)
to Maemo 7 / Leste by Arno_11 - 2 days, 5 hrs ago -
Install Fonts in N900 (68)
to Maemo 5 / Fremantle by teroyk - 3 days, 8 hrs ago - more...
|
2011-11-25
, 22:29
|
|
Posts: 882 |
Thanked: 1,310 times |
Joined on Mar 2007
|
#872
|
Originally Posted by aenbacka
Yes, started happening all of a sudden and won't start anymore.
Has someone else experienced the Failed to initiate session error with the latest version?
(no debugging symbols found)
FATAL ERROR: Could not initiate session. Error reason: "Unable to open trace file"
Program received signal SIGSEGV, Segmentation fault.
0x402da988 in sp_session_set_connection_type () from /opt/qspot/lib/libspotify.so.10
0x402da988 <sp_session_set_connection_type+4024>: ldrb r0, [r9, #558]
|
|
2011-11-26
, 08:45
|
|
Posts: 564 |
Thanked: 693 times |
Joined on Apr 2010
|
#873
|
Originally Posted by solbrit
Indeed strange. What is the xterm output when it fails. Have you tried clearing the cache directory? In case you use auto-login you could also try to logout and then login manually again.
Strange...
Since I updated to version 1.0.0-2 yesterday QSpot will login ok but then apparently get stuck trying to load the playlists, so I get nowhere... What to do?
Btw, I have the same problem as Theseb, but in my case perseverence is the key. It usually takes several attempts for the app to launch ok. Sometimes just a couple, sometimes up to fifteen-twenty. And always launching from terminal. App icon never works.
|
|
2011-11-26
, 08:48
|
|
Posts: 564 |
Thanked: 693 times |
Joined on Apr 2010
|
#874
|
Originally Posted by ukki
Have you cleared the qspot cache dir? Is the /home/user/MyDocs/.qspot directory being created?
Yes, started happening all of a sudden and won't start anymore.
(no debugging symbols found)
FATAL ERROR: Could not initiate session. Error reason: "Unable to open trace file"
Program received signal SIGSEGV, Segmentation fault.
0x402da988 in sp_session_set_connection_type () from /opt/qspot/lib/libspotify.so.10
0x402da988 <sp_session_set_connection_type+4024>: ldrb r0, [r9, #558]
|
|
2011-11-26
, 08:53
|
|
Posts: 882 |
Thanked: 1,310 times |
Joined on Mar 2007
|
#875
|
Originally Posted by aenbacka
Deleted /home/user/MyDocs/.qspot, but still doesn't start and directory isn't created again.
Have you cleared the qspot cache dir? Is the /home/user/MyDocs/.qspot directory being created?
|
|
2011-11-26
, 11:58
|
|
Posts: 564 |
Thanked: 693 times |
Joined on Apr 2010
|
#876
|
Originally Posted by ukki
Thanks for the info, I will look into it.
Deleted /home/user/MyDocs/.qspot, but still doesn't start and directory isn't created again.
 |
|
2011-11-26
, 20:28
|
|
Posts: 126 |
Thanked: 59 times |
Joined on Jan 2011
|
#877
|
Originally Posted by aenbacka
Tried clearing cache and logout/login but no luck... Terminal says:
Indeed strange. What is the xterm output when it fails. Have you tried clearing the cache directory? In case you use auto-login you could also try to logout and then login manually again.
> set_stream 'QSpot'
Connection state: 0
MESSAGE (log): "20:22:18.436 I [ap:1766] Connecting to AP ap.spotify.com:4070"
Registering container callbacks..
Container callbacks registered..
Connection state: 4
MESSAGE (log): "20:22:18.636 I [offline-mgr:2143] Storage has been cleaned"
MESSAGE (log): "20:22:18.670 I [ap:1224] Connected to AP: 78.31.8.51:4070"
Connection state: 1
|
|
2011-11-26
, 20:49
|
|
Posts: 564 |
Thanked: 693 times |
Joined on Apr 2010
|
#878
|
Originally Posted by solbrit
Seems that you are logged in ok at least. Do you start QSpot with an active internet connection or in offline mode? Do you have many playlists?
Tried clearing cache and logout/login but no luck... Terminal says:
> set_stream 'QSpot'
Connection state: 0
MESSAGE (log): "20:22:18.436 I [ap:1766] Connecting to AP ap.spotify.com:4070"
Registering container callbacks..
Container callbacks registered..
Connection state: 4
MESSAGE (log): "20:22:18.636 I [offline-mgr:2143] Storage has been cleaned"
MESSAGE (log): "20:22:18.670 I [ap:1224] Connected to AP: 78.31.8.51:4070"
Connection state: 1
|
|
2011-11-26
, 23:33
|
|
Posts: 126 |
Thanked: 59 times |
Joined on Jan 2011
|
#879
|
Originally Posted by aenbacka
I have about 20 playlists, but they used to load just fine in a second or two... And yes, I start with an active internet connection.
Seems that you are logged in ok at least. Do you start QSpot with an active internet connection or in offline mode? Do you have many playlists?
| The Following User Says Thank You to solbrit For This Useful Post: | ||
|
|
2011-11-27
, 08:06
|
|
Posts: 42 |
Thanked: 37 times |
Joined on Nov 2010
|
#880
|
I've found the same problem as ukki.
$ /opt/qspot/bin/qspot
> set_stream 'QSpot'
FATAL ERROR: Could not initiate session. Error reason: "Unable to open trace file"
Segmentation fault
~ $
I've deleted (moved away) /home/.config/qspot/qspot.conf and the result is the same, and file is not re-created.
So I've created an strace output file for you to be able to debug better this behaviour.
~ $ strace -o MyDocs/qspot.strace /opt/qspot/bin/qspot
(attached, gzip compressed, qspot.strace.gz)
Thanks for this great app I use almost every day!
Rafa.
$ /opt/qspot/bin/qspot
> set_stream 'QSpot'
FATAL ERROR: Could not initiate session. Error reason: "Unable to open trace file"
Segmentation fault
~ $
I've deleted (moved away) /home/.config/qspot/qspot.conf and the result is the same, and file is not re-created.
So I've created an strace output file for you to be able to debug better this behaviour.
~ $ strace -o MyDocs/qspot.strace /opt/qspot/bin/qspot
(attached, gzip compressed, qspot.strace.gz)
Thanks for this great app I use almost every day!
Rafa.
| The Following User Says Thank You to rgodinez For This Useful Post: | ||
 |
| Tags |
| premium account, spotify |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 01:50.
Since I updated to version 1.0.0-2 yesterday QSpot will login ok but then apparently get stuck trying to load the playlists, so I get nowhere... What to do?
Btw, I have the same problem as Theseb, but in my case perseverence is the key. It usually takes several attempts for the app to launch ok. Sometimes just a couple, sometimes up to fifteen-twenty. And always launching from terminal. App icon never works.