mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #77] Won't play next track on Raspberry Pi 3 #66
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#66
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sashahilton00 on GitHub (Jan 29, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/77
Saturday Aug 19, 2017 at 13:23 GMT
Originally opened as https://github.com/plietar/librespot/issues/234
I'm running librespot on an RPi 3 using a precompiled binary from https://github.com/herrernst/librespot/releases. The version reports itself as
INFO:librespot: librespot cc9dba8 (2017-03-26). Built on 2017-07-17. Build ID: 8zQE3BpbThe issue I have is, when my wife or I are trying to play songs from Spotify on our (Android) phones, we can only listen to one track and then playback stops (although the phone screens show that they are still connected and playing).
When the track changes I get this output when running from command line:
I don't see anything particularly troubling in that output.
Does anyone have any idea what the problem may be?
@sashahilton00 commented on GitHub (Jan 29, 2018):
Wednesday Sep 06, 2017 at 18:36 GMT
I have the same issue - I think it's related to https://github.com/plietar/librespot/issues/156
@ComlOnline commented on GitHub (Jan 29, 2018):
plietar#156 is now #44 here.
@ComlOnline commented on GitHub (Jan 29, 2018):
Please continue discussion for this in #103, as it seems to be same bug.