[GH-ISSUE #418] No warnings but no playback on multiple platform with 0.1.0 and latest develop: potential API changes? #271

New issue

Closed

opened 2026-02-27 19:29:45 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 19:29:45 +03:00

Owner

Originally created by @markubiak on GitHub (Jan 2, 2020).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/418

Hello,

I've been using librespot for years now, but sometime in the last week, my Pi stopped working with librespot. The log shows that the track is loaded after connection, but even when loaded (which seems to take much longer than it used to), the play and pause commands never seem to make it to Librespot. My desktop shows the song as playing, but Librespot does not. When the device transitions to the next song, the desktop client disconnects from Librespot. Again, the server running the binary shows no warnings or information other than "Loading ..." and sometimes "Loaded ".

I can reproduce this with 0.1.0 built from master, 0.1.0 from crates.io, and the latest dev branch. I also tried running librespot on my desktop (x86_64) installed with cargo, and see an identical issue. This leads me to believe something changed upstream.

This project actually got me to start learning rust, so if someone else can verify it's a code issue, I could be willing to take a look and see if I can take a crack at fixing it. Thanks

Originally created by @markubiak on GitHub (Jan 2, 2020). Original GitHub issue: https://github.com/librespot-org/librespot/issues/418 Hello, I've been using librespot for years now, but sometime in the last week, my Pi stopped working with librespot. The log shows that the track is loaded after connection, but even when loaded (which seems to take much longer than it used to), the play and pause commands never seem to make it to Librespot. My desktop shows the song as playing, but Librespot does not. When the device transitions to the next song, the desktop client disconnects from Librespot. Again, the server running the binary shows no warnings or information other than "Loading <track>..." and sometimes "Loaded <track>". I can reproduce this with 0.1.0 built from master, 0.1.0 from crates.io, and the latest dev branch. I also tried running librespot on my desktop (x86_64) installed with cargo, and see an identical issue. This leads me to believe something changed upstream. This project actually got me to start learning rust, so if someone else can verify it's a code issue, I could be willing to take a look and see if I can take a crack at fixing it. Thanks

kerem closed this issue

2026-02-27 19:29:45 +03:00

kerem commented

2026-02-27 19:29:46 +03:00

Author

Owner

@markubiak commented on GitHub (Jan 3, 2020):

Some updates: I can reproduce this on 3 machines, identical behavior for all. On one of the machines, I was also able to run librespot-java successfully and that program does not share this behavior. I've also found that "no playback" is not correct, but there is a 30+ second delay (check out the timestamps). After the song finally starts, it frequently drops out and back in.

I've attached debug logs for librespot and librespot-java for the same flow (host server, play on Android phone, connect to librespot, detach). Same behavior happens when using a Linux desktop client to connect to librespot.

@markubiak commented on GitHub (Jan 3, 2020): Some updates: I can reproduce this on 3 machines, identical behavior for all. On one of the machines, I was also able to run librespot-java successfully and that program does not share this behavior. I've also found that "no playback" is not correct, but there is a 30+ second delay (check out the timestamps). After the song finally starts, it frequently drops out and back in. I've attached debug logs for librespot and librespot-java for the same flow (host server, play on Android phone, connect to librespot, detach). Same behavior happens when using a Linux desktop client to connect to librespot.

kerem commented

2026-02-27 19:29:46 +03:00

Author

Owner

@markubiak commented on GitHub (Jan 7, 2020):

The issue went away today, with no code changes. The only thing I can think of is an issue on my LAN -- quite bizzare. I will reopen this if I encounter it again.

@markubiak commented on GitHub (Jan 7, 2020): The issue went away today, with no code changes. The only thing I can think of is an issue on my LAN -- quite bizzare. I will reopen this if I encounter it again.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/librespot#271

No description provided.

Rows
Columns