-
Notifications
You must be signed in to change notification settings - Fork 452
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
spotifyd keeps skipping to next song without playing anything #1299
Comments
I've just tried to edit the dependency to librespot to point to the dev branch. Due to conflicts on the dependencies of this branch and the version in the lock file, this requires to run Unfortunately it seems that librespot api has quite changed in the dev branch and the build fails (missing fields on enums and structs, invalid type un function args, ...) , it will require more work than what I hoped. Given that I know nothing about spotifyd nor librespot code base, I'm afraid I'll not be able ti fix this by myself 😞 |
The dev branch on librespot works just fine, you can migrate to that project for now. I don't think the repo maintainer would be happy to merge the code that depends on librespot dev-5.0.0 code that hasn't been released yet. @eladyn any thoughts on that? |
Yes, you're right, I'm switched to librespot as a workaround and it works fine. The main reason for creating this issue was to trace the issue for other spotifyd users who encounter it. |
There is supposed to be a workaround (add "0.0.0.0 apresolve.spotify.com" to /etc/hosts): For me, the workaround does not work, unfortunately. I am thankful for any other solution. |
That workaround used to work, but has stopped working recently. See the latest replies in the linked thread. Seems you can use librespot's dev branch, or alternatively I got https://github.com/devgianlu/go-librespot to work (after configuring |
For anyone else encountering the same issues, see my comment here: |
I made a quick workaround for this problem in my fork by updating librespot to v0.4.2 just check it out and compile it yourself afaik signing into your account is broken in general, that's a problem of librespot and not of spotifyd, so you have to use it without an account and I just noticed that there's a pull request already #1301 |
Seems to work great so far. |
I spoke too soon. It's happening again. |
still works for me. what's the issue you have? |
After maybe 15 minutes of listening and searching for new music I like (so sampling several tracks from different artists) it started playing up the same as before. ie. random track selection, play for a few seconds then select another random track like it's possessed. A reboot sorted it but I'm now trying https://github.com/lordievader/spotifyd to see if that's any different. |
then maybe something else is wrong with your system. it's the exact same fix lordievader did |
Comparing side by side it looks like you've made more changes and some formatting alterations? Although I'm no expert in these matters! I'm running it on a PiZero 2W with DietPi if that offers any clues. |
Note librespot is currently affected by other playback issues, e.g. librespot-org/librespot#1340 which I'm also running into with @Exceen's patched version. For me the crash means spotifyd will restart (and need to be reselected as an output in the desktop Linux client) - but I can imagine the behavior might be different depending on your setup. tl;dr check spotifyd logs |
Nope, no different. After 10 minutes it's skipping through tracks itself again. Unable to select anything or play anything. |
Description
For a few days spotifyd does not play any song (it's been working flawlessly for years) and instead keeps jumping to the next song in the queue. When looking at the logs, it complains about failing to load the track.
A quick search show that raspotify (dtcooper/raspotify#670 ) and librespot (librespot-org/librespot#1322) have the same issue, which is linked to a change on spotify side.
A fix has already been implemented in the dev branch, so it just switching to that branch might do the trick.
To Reproduce
Simply trying to play any song.
Expected behavior
Logs
Click to show logs
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: