-
Notifications
You must be signed in to change notification settings - Fork 185
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 not working anymore ? #203
Comments
Maybe try a newer version first? Your's is from 2016. |
i have tried. new rust, new cargo. new librespot from git. trying to compile ends in:
|
Did you exec |
not, i didn't. but with cargo clean same error. not able to install rust-crypto error: failed to run custom build command for if i only run cargo build --release the compiling works, bit wihtout pulseaudio support. and i need pulse |
Have you tried cross compiling it? Reading up on the error, it appears to occur when building rust crypto on i386-unknown-Linux-gnu. Try cross compilation and see if it builds |
No chance. Building the binary and execute it ends in erros. Does librespot do not support 32 bit environment anymore ?
|
and build another binary, still the same. no error in compiling. starting librespot now comes up with
|
You still have an active premium account? |
i just compiled with cargo build --release --no-default-features --features pulseaudio-backend instead of cargo build --release --features pulseaudio-backend Yes, i definatelly have a premium account .-) So,i at the moment i updated my os from wheezy to jessie . Maybe this will help ? With docker i wasnt be able to cross compile. |
Last time I tried to run on a Wheezy system I found the version of libc was too old |
Both runtime errors sound like a network problem to me. Do you have a default IPv4 route to the internet? And no firewall or the like blocking stuff? |
Maybe the ip range is blocked from spotify ? I can see in the spotify app the conntcted client multihome, if i tried to connect it fails. there is no error output and the client is not visible anymore.
so everything looks fine. shit. i loved librespot and i switched back to spotify from tifal cause of librespot . tidal supports dlna/upnp.
EDIT by @plietar, fixed the formatting of snippets. In the future please wrap them in triple backticks, it makes them much simpler to read |
OK. Got it working. I have done so many things that i can't really say why it now works. Maybe the upgrade to jessie .-) Thanks for your help. Yes, next time i will do a better formated post. Thread could be closed |
I've also tried with pulseaudio on an old Ubuntu running on an 32bit x86 box, and it worked, compiled with: |
hi, i have nothing changed in system. since a while i start librespot, the device is visible. trying to connect will timeout and the device is not visible anymore.
got no erros with backtrace. anyone a hint for me ?
multihome:/var/log# su mpd
mpd@multihome:/var/log$ RUST_BACKTRACE=1 /usr/bin/librespot /root//spotify-connect-web-chroot/usr/src/app/spotify_appkey.key --username XXX--password XXX--bitrate 320 --name XXX--backend pulseaudio
INFO:librespot::main_helper: librespot 7fd8503 (2016-12-30). Built on 2016-12-30.
INFO:librespot::session: Connecting to AP gew1-accesspoint-b-2d7t.ap.spotify.com:4070
INFO:librespot::session: Authenticated !
DEBUG:librespot::audio_backend::pulseaudio: Using PulseAudio sink
The text was updated successfully, but these errors were encountered: