Triode wrote:
It is intended to log out on idle - are you actually experiencing
problems playing tracks?
Sometimes yes, but I'm wondering now if it's not perhaps unrelated to
the password thing.
Spotify log says this:
Code:
[10:11:00.383527] main:591 req:
w.irving wrote:
Sometimes yes, but I'm wondering now if it's not perhaps unrelated to
the password thing.
Spotify log says this:
Code:
[10:11:00.383527] main:591 req: browse.json res:
spotify:track:3suJb4ZzNTHMEWq3WxIC0T par: (null) prot: HTTP/1.0 auth:
I've been having this problem too, with 2.2.16 on Linux. After a
seemingly random amount of time, spotify is no longer logged in.
/var/lib/squeezeboxserver/prefs/plugin/spotify.prefs contains
Code:
password: ''
even after logging in (maybe supposed
w.irving wrote:
I've been having this problem too, with 2.2.16 on Linux. After a
seemingly random amount of time, spotify is no longer logged in.
/var/lib/squeezeboxserver/prefs/plugin/spotify.prefs contains
Code:
password: ''
even
Triode wrote:
Has anyone managed to try this yet?
Hi,
Spotify plugin v. 2.2.16 working perfectly on ReadyNas Ultra 4 and 6.
No issues concerning lost password.
Thanks.
Kr
Kim K
Kim Kruse's Profile:
Triode wrote:
I should have made this a new post so people see it and hopefully test:
I've added version 2.2.16 to my repository
http://triodeplugins.googlecode.com/svn/trunk/repo.xml for linux which I
hope fixes this. Once I have a couple of positive responses to the linux
version I will
I should have made this a new post so people see it and hopefully test:
I've added version 2.2.16 to my repository
http://triodeplugins.googlecode.com/svn/trunk/repo.xml for linux which I
hope fixes this. Once I have a couple of positive responses to the linux
version I will roll out to other
MALmen wrote:
Enable caching seems to have solved the problem... I don't really wan't
that enabled though.. 10% of 5.4 TB i quite much space :S
Hum - this looks like a bug - disabling caching also disables storing of
the password... I will look at this. It may be that I need to set the
Hello! I also have trouble remebering the password on m Synology NAS.
After reboot it Always says Password not set and as a result of this i
can't login :/ If i enter the password again it works but is lost after
reboot :/
MALmen wrote:
Hello! I also have trouble remebering the password on m Synology NAS.
After reboot it Always says Password not set and as a result of this i
can't login :/ If i enter the password again it works but is lost after
reboot :/
Is this definately the case with 2.2.15 as this fixed
Triode wrote:
Is this definately the case with 2.2.15 as this fixed some issues
relating to this?
Yes :/
MALmen's Profile: http://forums.slimdevices.com/member.php?userid=60693
View this thread:
MALmen wrote:
Yes :/
What error messages do you see in the helper app log?
Triode's Profile: http://forums.slimdevices.com/member.php?userid=17
View this thread: http://forums.slimdevices.com/showthread.php?t=99118
Triode wrote:
What error messages do you see in the helper app log?
[23:30:33.399315] main:1595 bad request for socket or no track
[23:30:33.416853] main:586 req: browse.json res:
spotify:track:11upvZJSdEM67OeehyxLqt par: (null) prot: HTTP/1.0 auth:
(null)
[23:30:33.416964] main:686 no
MALmen wrote:
[23:30:33.399315] main:1595 bad request for socket or no track
[23:30:33.416853] main:586 req: browse.json res:
spotify:track:11upvZJSdEM67OeehyxLqt par: (null) prot: HTTP/1.0 auth:
(null)
[23:30:33.416964] main:686 no remembered user
[23:30:33.417088] main:1595 bad request
Triode wrote:
And when you add the password what does it say?
[00:03:59.137826] main:534 new connection
[00:03:59.138908] main:644 attempting login for user: 115783854
[00:03:59.139091] log_message:80 log: 22:03:59.139 I
[offline_authorizer.cpp:289] Unable to login offline: no such user
MALmen wrote:
[00:03:59.137826] main:534 new connection
[00:03:59.138908] main:644 attempting login for user: 115783854
[00:03:59.139091] log_message:80 log: 22:03:59.139 I
[offline_authorizer.cpp:289] Unable to login offline: no such user
[00:03:59.139470] log_message:80 log: 22:03:59.139
Triode wrote:
So it looks lib libspotify is having a problem saving files - this will
prevent the password being stored. You should check why files can't be
saved.
Where are those files stored? I tried to reinstall plugin without luck
:/
Triode wrote:
So it looks lib libspotify is having a problem saving files - this will
prevent the password being stored. You should check why files can't be
saved.
Enable caching seems to have solved the problem... I don't really wan't
that enabled though.. 10% of 5.4 TB i quite much space
I must say that I am VERY embarassed and ashamed to have been such a
waste of your time!!
Found out now that the plugin was workin' very well (maybe even all the
time since I entered the password with admin credentials) - but I was
stupidly just checking the 'not logged in' message and wrongfully
I've been puzzled by this, maybe someone can help:
After a full OS reinstall on SSD, including LMS, the triode plugin does
not remember the password to login to spotify. Whatever I try, after a
reset of the plugin it is lost again. When I enter it manually all works
fine (until the next
SlimPvC wrote:
I've been puzzled by this, maybe someone can help:
After a full OS reinstall on SSD, including LMS, the triode plugin does
not remember the password to login to spotify. Whatever I try, after a
restart of the server it is lost again and has to be entered manually.
When I
Triode wrote:
Recent versions of the plugin so not store the password itself, they set
it in libspotify when the password is added and apply clicked. This
means the location where libspotify stores its settings is where the
password is stored (in encrypted form). By doing this it is more
SlimPvC wrote:
Thanks for your quick answer, but it's not exactly clear to me what to
do now.
From what I understand it may be libspotify that does not retain the
password?
- i have now disabled (unchecked) the 'disable cache' setting since that
does not seem to be right to be checked
Makes no difference: as soon as the LMS is stopped, the password setting
is lost.
All other entries (such as the settings for last.fm login etc.) remain
intact; it's only the password that vanishes...
I wonder if this could have anything to do with the installation on a
SSD drive? Though I
SlimPvC wrote:
Makes no difference: as soon as the LMS is stopped, the password setting
is lost.
All other entries (such as the settings for last.fm login etc.) remain
intact; it's only the password that vanishes...
I wonder if this could have anything to do with the installation on a
I know, I always check by looking at the status, which says 'currently
not logged in' etc.
Helper log is set to 'errors' and shows not too much details. I'll set
it to 'debug' and will report later.
Thanks,
Peter
SlimPvC wrote:
I know, I always check by looking at the status, which says 'currently
not logged in' etc.
Helper log is set to 'errors' and shows not too much details. I'll set
it to 'debug' and will report later.
Thanks,
Peter
It only tries to log in when you use it - the error you
Triode wrote:
It only tries to log in when you use it - the error you are looking for
is bad password or something like that. Not logged in is quite normal.
H - could it be there was no problem at all all the time and I was
just on the wrong track by this 'not logged in' thing!?!
I'll
28 matches
Mail list logo
