You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running udev monitor or aplay -l will show that both udev and ALSA are picking up the sound card. However running pactl list sinks will yield no result. PulseAudio is ignoring the udev events it seems.
If you invert the order of operations however hotplugging works as intended:
Connect a USB sound card to your device
Start audio block
This might be related to how systemd ALSA rules are handled, and how PulseAudio interacts with that (seems a bit sketchy?). Some references here for further investigation:
I'd guess this could be kernel or alsa-lib issue so please re-test. The error reported looks almost like if kernel alsa layer created /dev/snd/ entry (which is getting picked by pulseaudio udev monitoring routine) before kernel alsa driver completed all things required for alsa-lib to actually use the device successfully - this should never happen.
I know this has been ages, but was any progress made on this? That jellyfish URL seems to be invalid.
We're having issues with a container starting up and even when the USB device is plugged in, it doesn't always recognize it in time. Even when it does, no hot swapping seems to work. When this occurs, after boot, there's no sound card discovered and no way to fix it without restarting the service, which starts the process over and may still not fix it.
To replicate
Running
udev monitor
oraplay -l
will show that both udev and ALSA are picking up the sound card. However runningpactl list sinks
will yield no result. PulseAudio is ignoring the udev events it seems.If you invert the order of operations however hotplugging works as intended:
This might be related to how systemd ALSA rules are handled, and how PulseAudio interacts with that (seems a bit sketchy?). Some references here for further investigation:
The text was updated successfully, but these errors were encountered: