mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #240] Is this project alive / librespot stop being visible without error #161
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#161
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 @michalfita on GitHub (Jul 23, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/240
Since 18 May there is no commits to main repository - plenty of forks are alive and active, but raspotify uses code from here. Is this project alive?
I have serious issues with librespot that annoys whole family. Suddenly without any error message in logs it stops being visible as Spotify Connect device. I have to login and restart the whole service to get it back.
Would be nice if it at least crashes, so systemd would be able to restart. Any hints or predictions when it could be fixed? Maybe one of forkers already have a solution for that?
@ComlOnline commented on GitHub (Aug 2, 2018):
Sorry, I have beeing working at a summer camp for the last few months, that all ends in a few days so Ill have a lot more time to look after this.
Do you have anymore information about your install? What version are you using?
Many Thanks
@SirJson commented on GitHub (Aug 4, 2018):
Might be related to #172? I frequently run into this bug and if no one else fixes it by the time I get librespot working with my application again then I will maybe fix that...
@michalfita commented on GitHub (Aug 6, 2018):
So, my symptoms are like in #241. The log shows:
I started to think about writing a log filter in Python to restart the librespot on each occurrence of the time out.
It can work for a few days without a problem, but when the internet connection is down (due to provider issues), then it will not work any more without restarting. As long as librespot is working as standalone process, can you exit gracefully in case of trouble? Systemd will solve the issue by starting the process again.
libresport doesn't have --version option, so I can't display it's version. It's coming from most recent raspotify as of today. All running on regularly updated Raspbian Stretch.
@sashahilton00 commented on GitHub (Aug 6, 2018):
The project is still alive, though there hasn't been much activity in the past couple of months, as the core maintainers have been/are busy, and there haven't been many pull requests. I note there are lots of forks adding functionality, if people want that added to the main repo, feel free to open a PR.
@sashahilton00 commented on GitHub (Aug 6, 2018):
Closing as main question resolved. For secondary question, refer to #172
@michalfita commented on GitHub (Aug 6, 2018):
Another session error causing trouble:
Again, only restart helps.