[Jaunty] Sound channels are muted after reboot

Bug #316430 reported by Ivan Stetsenko
52
This bug affects 9 people
Affects Status Importance Assigned to Milestone
alsa-utils (Ubuntu)
Fix Released
Low
Daniel T Chen
udev (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: alsa-utils

The bug is really similar to bug 299093. After reboot the majority of channels in the alsamixer -c 0 are muted, so that no sound can be heard.

alsa-utils 1.0.18-1ubuntu5
alsa-base 1.0.18.dfsg-1ubuntu2

stetzen@stetzen-laptop:~$ cat /proc/asound/cards
 0 [Intel ]: HDA-Intel - HDA Intel
                      HDA Intel at 0xfe100000 irq 17

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)

Revision history for this message
Ivan Stetsenko (stetzen) wrote :
Revision history for this message
Sebastian Keller (skeller) wrote :

I can confirm this problem on my laptop.

In /var/lib/alsa/asound.state it looks like the mixers should be turned up.
Also the following works:
sudo /etc/init.d/alsa-utils stop
alsamixer -c0
#changing some levels
sudo /etc/init.d/alsa-utils start
#everything is reset again to the level before stop like it is to be expected.

alsa-utils 1.0.18-1ubuntu6
alsa-base 1.0.18.dfsg-1ubuntu2

cat /proc/asound/cards
 0 [ICH6 ]: ICH4 - Intel ICH6
                      Intel ICH6 with AD1981B at irq 22

00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)

Changed in alsa-utils:
status: New → Confirmed
Revision history for this message
Daniel T Chen (crimsun) wrote :

Please attach, separately, the contents of /var/lib/alsa/asound.state and the output from `amixer -Dhw:0'. (Be sure to also include a separate `amixer -Dhw:$i' output for each $i that corresponds to card indices in /proc/asound/cards.)

Revision history for this message
Sebastian Keller (skeller) wrote :
Revision history for this message
Sebastian Keller (skeller) wrote :
Revision history for this message
Sebastian Keller (skeller) wrote :
Revision history for this message
Sebastian Keller (skeller) wrote :
Revision history for this message
Sebastian Keller (skeller) wrote :

I think I found the problem:

sebastian@sebastian-laptop:~$ /lib/udev/alsa-utils
.: 11: Can't open /lib/udev/hotplug.functions

sebastian@sebastian-laptop:~$ dpkg -S hotplug.functions
dpkg: *hotplug.functions* not found.

Revision history for this message
Sebastian Keller (skeller) wrote :

Commenting the two lines which referenced that file/functions from that file made it work again.

I'm adding udev to this report as this is the package where the according file is included in Debian.

Revision history for this message
Daniel T Chen (crimsun) wrote :

The issue is solely the fault of alsa-utils's incorrect udev.script.

Changed in udev:
status: New → Invalid
Changed in alsa-utils:
assignee: nobody → crimsun
importance: Undecided → Low
status: Confirmed → Fix Committed
Revision history for this message
John S. Gruber (jsjgruber) wrote :

I can confirm that deleting those two lines solves my case as well.

@Daniel:

In udev rules is forking a process which waits for a file or files deprecated?

I notice that the hotplug.functions file is added to udev with a debian patch and that Ubuntu no longer uses the debian udev package.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package alsa-utils - 1.0.18-1ubuntu7

---------------
alsa-utils (1.0.18-1ubuntu7) jaunty; urgency=low

  [ Daniel T Chen ]
  * Add fixes from git:
    - force_state_reinit_when_new_mixer_elements_exist.patch,
    - fix_possible_fpe_speaker-test.patch
  * Ensure sound channels are not muted after reboot. (LP: #316430)

  [ Luke Yelavich ]
  * unset_pulse_internal.patch: We don't want alsamixer to show the pulse
    mixer by default, since it can be controlled from pulseaudio itself.

 -- Luke Yelavich <email address hidden> Mon, 19 Jan 2009 10:43:28 +1100

Changed in alsa-utils:
status: Fix Committed → Fix Released
Revision history for this message
Noel J. Bergman (noeljb) wrote :
Revision history for this message
Sean Parsons (ubuntu-futurenotfound) wrote :

I'm getting a situation where the login sounds play, but the GNOME mixer seems to think there's no output devices and similarly I get no sound in things like the Movie Player.

The usual suspects look like this:
$ cat /proc/asound/cards
 0 [Intel ]: HDA-Intel - HDA Intel
                      HDA Intel at 0xfe9fc000 irq 21
$ lspci | grep -i audio
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)

Revision history for this message
Sebastian Keller (skeller) wrote :

That is a different bug. I guess it is some kind of race condition what gets started first, either pulseaudio or the canberra startup sound. If you don't have alsa configured to use pulseaudio, then canberra, if it gets started before pulse, probably detects that no pulseaudio is running and then uses alsa to play the sound, thereby locking the alsa device. If pulse gets started during that time it can't access the alsa device because of that.

Revision history for this message
David Henningsson (diwic) wrote :

Sean, you're probably experiencing bug #322374

Revision history for this message
Michael Tsang (michaeldadmum-deactivatedaccount) wrote :

Although this bug is fixed, alsa-utils is still shipping with muted defaults so there is no sound after a fresh ubuntu install.

Revision history for this message
Ricardo Pérez López (ricardo) wrote :

I still have the same problem in my fully updated Jaunty: no sound after boot. However, the issue is not always reproducible: sometimes the audio is properly restored after boot, and sometimes is muted.

$ cat /proc/asound/cards
 0 [VT82xx ]: HDA-Intel - HDA VIA VT82xx
                      HDA VIA VT82xx at 0xdfdfc000 irq 17

Revision history for this message
Andrew (andrewabc) wrote :

I installed fresh 9.04 x64 ext4, and I seem to get mute on boot. And when I unmute it and make sure PCM volume is turned up there is still no sound. Last night I was able to fix it by selecting other sound options (cards?) and eventually went back to my HDA Intel (alsa mixer) and PCM was set to bottom even though I made sure it was turned up before. I turned it up and sound worked. But today I try this and it PCM is still shown as turned up all the way.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.