broken user requires removal before asoundconf will correctly set configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
asoundconf-gtk (Ubuntu) |
Incomplete
|
Undecided
|
Daniel T Chen |
Bug Description
Binary package hint: alsamixergui
alsamixer does not find default device:
mcarro@balboa:~$ alsamixer
alsamixer: function snd_ctl_open failed for default: No such device
However, "alsamixer -c 0" does start normally. This bug affects other applications which try to use the "default" sound device -- e.g., gcompris, which fails to deliver sound with the following error messages:
ALSA lib confmisc.
ALSA lib conf.c:
ALSA lib confmisc.
ALSA lib conf.c:
ALSA lib confmisc.
ALSA lib conf.c:
ALSA lib conf.c:
ALSA lib pcm.c:2144:
No configuration file was manually edited at any moment.
Changed in alsamixergui: | |
status: | New → Confirmed |
Changed in alsa-utils: | |
assignee: | nobody → crimsun |
Comment from the same person who reported the bug:
I have sound using the "default" device again. I removed the .asoundrc. asoundconf file and run asoundconf-gtk to select again the default card. The previous .asoundrc. asoundconf file had, as default, a card which was probably corresponding to an USB device which I tried to make the default device and which is not plugged in now. However, asoundconf-gtk did not give me any option to set the default sound card before I removed the .asoundrc. asoundconf files. I think that this counds as a bug: a buggy (or non-current) alsa user conf file prevents asoundconf-gtk from generating a correct configuration.