Martin_z;696186 Wrote: > Well, unfortunately, the self test now complains that the helper isn't > working. I tried doing a search (directly on the SB) but it complained > about a bad search params (see log below) - and then I tried a radio > search and it segfaulted. May or may not be associated? > > > [18:13:11.077016] main:366 ./spotifyd 2.2.2 started > [18:13:11.078193] main:386 Config: username: zelemo cachedir: > /var/lib/squeezeboxserver/cache/spotifycache bitrate: 160 volnorm: 0 > httpport: 9005 cliport: 9090 > [18:14:21.044702] main:475 new connection > [18:14:21.048618] main:579 attempting login for user: zelemo > [18:14:21.905039] log_message:74 log: 18:14:21.904 I [ap:1766] > Connecting to AP ap.spotify.com:4070 > [18:14:22.124333] log_message:74 log: 18:14:22.124 I [ap:1224] > Connected to AP: 78.31.8.19:4070 > [18:14:22.918212] log_message:74 log: 18:14:22.918 I [user_cache:138] > UserCache::initiateGetUsers() will query for 1 users > [18:14:24.045049] logged_in:47 logged in > [18:15:36.053126] main:475 new connection > [18:15:36.057412] main:535 logging out before setting password > [18:15:36.064062] main:547 waiting for logout to complete > [18:15:36.064292] logged_out:54 logged out > [18:15:37.064472] main:579 attempting login for user: zelemo > [18:15:38.164849] log_message:74 log: 18:15:38.164 I [ap:1766] > Connecting to AP ap.spotify.com:4070 > [18:15:38.177151] log_message:74 log: 18:15:38.177 I [ap:1224] > Connected to AP: 78.31.8.42:4070 > [18:15:40.277130] logged_in:47 logged in > [18:16:51.108891] main:475 new connection > [18:16:51.118658] main:535 logging out before setting password > [18:16:51.119380] main:547 waiting for logout to complete > [18:16:51.119573] logged_out:54 logged out > [18:16:52.119744] main:579 attempting login for user: zelemo > [18:16:53.224862] log_message:74 log: 18:16:53.224 I [ap:1766] > Connecting to AP ap.spotify.com:4070 > [18:16:53.262664] log_message:74 log: 18:16:53.262 I [ap:1224] > Connected to AP: 78.31.8.15:4070 > [18:16:56.326883] logged_in:47 logged in > [18:17:08.058659] main:475 new connection > [18:17:08.063435] main:521 req: search.json res: (null) par: > o=0&arq=10&alq=10&trq=10&q= prot: HTTP/1.0 auth: (null) > [18:17:08.063549] main:1064 bad search params > [18:17:22.424871] main:475 new connection > [18:17:22.429670] main:521 req: search.json res: (null) par: > o=0&arq=10&alq=10&trq=10&q= prot: HTTP/1.0 auth: (null) > [18:17:22.429785] main:1064 bad search params > [18:17:40.506263] main:475 new connection > [18:17:40.532289] main:521 req: radio.json res: (null) par: > s=1900&e=2020&g=1 prot: HTTP/1.0 auth: (null) > [18:17:40.532409] main:1284 radio query start year: 1900 end year: 2020 > genre mask: 1 > [18:17:40.532899] main:1291 created radio search > Segmentation fault
Hum - that doesn't look good - could you set the log level to TRACE (manually edit the config file for that) and restart the process manually. This should create a tracefile in the same directory which should show what the last libspotify call is made when it crashes (if it crashes in lib spotify or help be find where in my code) "General transient error" means an error occured in the spotify library or their backend. Unfortunately they don't give any more error messages. -- Triode ------------------------------------------------------------------------ Triode's Profile: http://forums.slimdevices.com/member.php?userid=17 View this thread: http://forums.slimdevices.com/showthread.php?t=79706 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
