-
-
Notifications
You must be signed in to change notification settings - Fork 220
EBUSY: Device or resource busy #205
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
Comments
I think I have a very similar issue. Trying to use DragonFly USB DAC, getting either one of two errors:
Then when I try to restart the raspotify service, I might get:
Any help is greatly appreciated. Funny thing is that a noname Chinese USB DAC worked just fine and when switching to DragonFly, can't get it to work. |
I'm having a similar issue using the Google Voice Kit. The daemon log shows this crash:
However, running /usr/bin/librespot directly on the terminal with the same arguments seems to work. |
In case anyone has this error and doesn't want to waste 2 hours as I did. in the configuration file at /etc/default/raspotify under options I added this." --device hw:1,0 " where the 1 represents the card and the 0 represents the device |
Hi all,
Since last update (with OSMC) can't get raspotify to work
Option line should be good
osmc@osmc:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: BossDAC [BossDAC], device 0: Boss DAC HiFi [Master] pcm512x-hifi-0 [] Subdevices: 0/1 Subdevice #0: subdevice #0
OPTIONS="--device plughw:0,0"
The log
* raspotify.service - Raspotify Loaded: loaded (/lib/systemd/system/raspotify.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2019-05-11 08:32:06 CEST; 17s ago Process: 13540 ExecStartPre=/bin/chown raspotify:raspotify /var/cache/raspotify (code=exited, status=0/SUCCESS) Process: 13537 ExecStartPre=/bin/mkdir -m 0755 -p /var/cache/raspotify (code=exited, status=0/SUCCESS) Main PID: 13543 (librespot) CGroup: /system.slice/raspotify.service
-13543 /usr/bin/librespot --name raspotify (osmc) --backend alsa --bitrate 160 --disable-audio-cache --enable-volume-normalisation --linear-volume --initial-volume=100 --device plughw:0,0May 11 08:32:19 osmc librespot[13543]: INFO:librespot_core::session: Authenticated as "blogonat" !
May 11 08:32:19 osmc librespot[13543]: INFO:librespot_playback::audio_backend::alsa: Using alsa sink
May 11 08:32:19 osmc librespot[13543]: INFO:librespot_core::session: Country: "FR"
May 11 08:32:19 osmc librespot[13543]: INFO:librespot_playback::player: Loading track "Lover Of The Light" with Spotify URI "spotify:track:73ZdoUAA4qgXrz7j30qirm"
May 11 08:32:20 osmc librespot[13543]: INFO:librespot_connect::spirc: Resolved 20 tracks from <"spotify:station:album:5DWkj0MS3zVHmFXHbjcwf6">
May 11 08:32:20 osmc librespot[13543]: INFO:librespot_playback::player: Track "Lover Of The Light" loaded
May 11 08:32:20 osmc librespot[13543]: ERROR:librespot_playback::audio_backend::alsa: Alsa error PCM open ALSA function 'snd_pcm_open' failed with error 'EBUSY: Device or resource busy'
May 11 08:32:20 osmc librespot[13543]: ERROR:librespot_playback::player: Could not start audio: Alsa error: PCM open failed
May 11 08:32:20 osmc librespot[13543]: ERROR:librespot_playback::audio_backend::alsa: Alsa error PCM open ALSA function 'snd_pcm_open' failed with error 'EBUSY: Device or resource busy'
May 11 08:32:20 osmc librespot[13543]: ERROR:librespot_playback::player: Could not start audio: Alsa error: PCM open failed
`
Many thanks !
The text was updated successfully, but these errors were encountered: