Wow, that seems to be the right direction (and I'm learning about linux): After a (clean) boot (resulting in a "dummy device" sound output) fuser gives the following:
$ sudo fuser -v /dev/dsp /dev/snd/* USER PID ACCESS COMMAND /dev/snd/controlC0: Slmodemd 1213 F.... slmodemd /dev/snd/pcmC0D6c: Slmodemd 1213 F.... slmodemd /dev/snd/pcmC0D6p: Slmodemd 1213 F.... slmodemd Following a "alsa force-reload" the output changes to: $ sudo fuser -v /dev/dsp /dev/snd/* USER PID ACCESS COMMAND /dev/snd/controlC0: bernhard 3827 F.... pulseaudio /dev/snd/pcmC0D0c: bernhard 3827 F...m pulseaudio /dev/snd/pcmC0D0p: bernhard 3827 F...m pulseaudio Yupp I realize that I made a typo missing an asterisk behind dsp, but I think the point is quite clear. At boot time, the smartlink modem daemon grabs all of the audiodevices. So it seems this bug is not really the fault of pulseaudio but of slmodemd! -- No sound with intel-hda without "alsa force-reload" https://bugs.launchpad.net/bugs/449762 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs