[Pkg-alsa-devel] Bug#406738: alsa-utils: Running alsaconf stops
sound card from working
dru at treshna.com
Mon Jan 15 21:34:14 UTC 2007
Steve Langasek wrote:
> severity 406738 normal
> tags 406738 unreproducible
> On Sun, Jan 14, 2007 at 03:52:23AM +1300, Dru wrote:
>> Running alsaconf stops my sound card from working. No errors appear for
>> playing sounds, nor are there any errors loading the modules for the
>> sound card. Alsaconf behaves as you would normally expect. But after
>> running it for the first time you can no longer output sound.
>> All sound based applications work fine, and continue to play music etc
>> though no sound is produced. Its like the sound is muted but volumes are
>> all fine when you check.
>> The only fix I could find for it was to do a purge on alsa-utils,
>> alsa-base, alsa-tools and then reinstall. After reinstalling all these
>> packages sound works perfectly fine again. Its only if you run alsaconf
>> does sound stop working.
>> I have a Creative Labs SB Audigy.
> I've never had to run alsaconf before. If you already had sound working,
> I'm not sure why you did either? But still, with my card running alsaconf
> doesn't break the sound; it works just as well after running alsaconf as it
> did before.
I ran it by accident. Thats why it was annoying. Was typing alsamixer
and hit c then tab instead. And it took me 4 hours to figure out what i
did to break it. Accidently running a programme shouldnt kill your
ability to produce sound. I properly configured it in alsaconf when it
> Please send the contents of the /etc/modprobe.d/sound file that was
> generated on your system by alsaconf.
Can you reproduce the results by running alsaconf?
> I'm downgrading this bug, because failing to configure sound correctly for
> one type of sound card does not make the package unusable.
More information about the Pkg-alsa-devel