randomsound prevents proper alsa/pulseaudio startup
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| randomsound (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
When randomsound is enabled, it causes "arecord" to grab exclusive use of some sound hardware, which prevents alsa from properly detecting the hardware. The end symptom is that there is no system sound, and the alsamixer (and other similar apps) show only a "Dummy Output" sound device.... The same problem caused by other services (e.g. "slmodem") has been fairly widely reported, as I found in googling.
I think the fix may be to adjust the upstart job to require that alsa starts first, if present, but I don't know how to do that...
FYI: here is output of "fuser /dev/snd/*", which led me to determine that randomsound was the problem:
/dev/snd/controlC0: root 1911 F.... arecord
/dev/snd/pcmC0D0c: root 1911 F...m arecord
/dev/snd/timer: root 1911 f.... arecord
Feel free to contact me for clarification if required.
Maverick; both gnome & kde;
| Mike Morris (mike-musicplace) wrote | #1 |
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in randomsound (Ubuntu): | |
| status: | New → Confirmed |
This is clearly a duplicate - sorry. I don't know how I missed the others when I searched... I *did* search :-)