Hey guys, On Sat, May 08, 2021 at 06:33:49PM +0200, Vincent Lefevre wrote: >FYI, other users got the same error: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848395 > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1568772 > https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1624435 > https://bugs.gentoo.org/578138 > >In Debian bug 848395: as said by the alsactl(1) man page: > > init tries to initialize all devices to a default state. > If device is not known, error code 99 is returned. > >I can see 2 possibilities: > >1. For some reason, the device is not always initialized by the > kernel. > >2. There is a race condition: alsactl is run too soon, while the > device has not been initialized yet by the kernel. > >(2) would explain why this isn't always reproducible.
I'm seeing what appears to be a very similar problem here *one my system running bookworm and 6.1.0-18-amd64 / 6.1.76-1. I have a USB dongle paired with a wireless headset. * If I hot-plug this in on my laptop, it initialises and shows up ~immediately in the pipewire<->pavucontrol stack. * If I hot-plug this on my desktop, it reproducibly fails to initialise with the same error mentioned here: Jul 05 20:04:21 lump (udev-worker)[332849]: controlC0: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with exit code 99. On the desktop system, if I kill one of the bits in the stack (e.g. pipewire-pulse), things re-initialise OK and the device shows up. I don't know if this data point is useful, but I thought it was worth sharing maybe. -- Steve McIntyre, Cambridge, UK. st...@einval.com "Arguing that you don't care about the right to privacy because you have nothing to hide is no different than saying you don't care about free speech because you have nothing to say." -- Edward Snowden
