mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #50] Main thread panicks when sound device unavailable #38
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#38
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/50
Friday Mar 17, 2017 at 07:55 GMT
Originally opened as https://github.com/plietar/librespot/issues/165
Using:
./librespot -n SpotifyMain -b 320 --backend portaudio --device "NAD USB Audio 2.0: - (hw:2,0)"
commit
eb49ff3on Ubuntu 16.04If the hardware is claimed by other software (or hardware not available) and spotify connect attempts to load a song, the main thread panicks & fails.
Suggestion is to make it fail gracefully and wait for the next command?
When started correctly and while paused, another program claims the soundcard:
on another occasion, starting librespot while device already claimed:
@sashahilton00 commented on GitHub (Jan 29, 2018):
Tuesday May 02, 2017 at 07:46 GMT
Same issue here.. I run librespot in conjunction with snapcast, so I don't even use an audiodevice.
@ComlOnline commented on GitHub (Jan 29, 2018):
@TonioRoffo @ashwinvandijk Do you know if you still have this issue?
@sashahilton00 commented on GitHub (Feb 7, 2018):
And if the issue does still exist, can you run with a backtrace?
@TonioRoffo commented on GitHub (Feb 7, 2018):
Sorry, no longer running librespot, can't assist further.
@sashahilton00 commented on GitHub (Feb 7, 2018):
Ok, not a problem, thanks for replying. @ashwinvandijk is this still an issue for you?
@sashahilton00 commented on GitHub (Feb 25, 2018):
No response, and no further reports, so closing. Please open a new issue with a backtrace if you are having this issue.