-
Notifications
You must be signed in to change notification settings - Fork 217
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
librespot error: Unable to load encrypted file: ChannelError #669
Comments
I encountered the same error today. It worked perfectly for months (thanks for that) but today I cannot play music anymore:
|
The recommended workaround from librespot is to recompile librespot from dev as mentioned in this comment. |
Same |
Hello, I propose this fix You can compile them yourself ( Or sillily trust me and download one of these installers. I had to make them this way (and not simply recompile upstream librespot branch dev) because my orange-pi-zero is not able to compile anything. It is now running the raspi version. This is a temporary fix and I hope @JasonLG1979 will fix this his way. |
I've attempted to mirror the fix (with both Docker & Podman) but so far it doesn't work for me. I am constantly running into packaging dependencies issues at compiling part in a Dockerfile. Seems I'll stick around with Librespot for some time. Doing it on Raspbian |
FWIW I ran it on ubuntu 22.04 / amd64. |
@RSKriegs I had two issues building: |
You can try and add edit fixed |
That's what I did to resolve it, other than those build run ok for me on Arch/amd64. The only thing to keep in mind is that tag that you set will conflict with existing version and if you use something lower it will warn of package downgrade and if you set newer, I'm not sure how update will work once fix is published in the repo. |
For me it's working again without any changes! Maybe Spotify reverted their change or it was just part of the service down? |
For me as well. Thank the heavens |
I wouldn't hold my breath though. Rumor has it that it's only a temporary rollback on Spotify's part. Hopefully in the meantime we can merge a working librespot version into raspotify |
|
I did this (please have mercy) and now listening happily. Many thanks. |
This patch uses upstream dev branch in favor of Jason's fork. The dev branch merged cleanly into that fork, and there was no diff between the two trees. Fixes dtcooper#670 Fixes dtcooper#669
Latest release 0.44.0 should address this issue. Please test! |
The update seems to work. Spotify finds my speaker, connects and plays music. So thanks for. I will do some further testing. W.r.t the autoplay flag, you have to use "on" or "off". e.g. LIBRESPOT_AUTOPLAY="off" |
@HendrikV37 the autoplay default flag was fixed and the updated config is in the 0.45.0 release. Thanks for testing, did you experience any more problems? |
No, seems to work fine now. |
Compatible Device
Are you sure?
Compatible OS
Compatible Configuration
Latest Version
Are you sure?
Due Diligence
What happened?
I've newly installed raspotify, first time I've tried it (apologies in advance if I've messed up). I've checked all packages are up to date. Able to connect but, so far, unable to play any tracks. The Spotify app it skips a number of tracks and then drops the connection. Raspotify crashes.
Relevant log output and/or the contents of /etc/raspotify/crash_report if any ( sudo journalctl -u raspotify -b and sudo cat /etc/raspotify/crash_report )
The text was updated successfully, but these errors were encountered: