Volume control setting itself to mute on reboot

[exploder91]

I am running Ubuntu Jaunty 9.04 32 bit, fully updated (March, 20th, 2009). I have on board HDA Intel sound on a Compaq desktop system. There is a problem with the new volume control. The volume control is randomly setting itself to mute. I notice the problem at start up and after rebooting but it does not happen every time, just at random intervals. I can un-check "mute" and turn the volume up and sound will work as it should.

I am not certain of the exact package name for what the cause of this bug is, sorry. I looked through the other bug reports displayed in Launchpad before creating this bug report and none of them seemed to match this exact problem.

[morryis (morryis)]

I can confirm this on several systems

[Tuomas Aavikko (taavikko)]

Changing affected package to "alsa-utils" which should be the correct one.
Also affected in here.

Up-to-date jaunty.

Haven't tested if this is random behaviour or happening on every boot.

[Brian Curtis (bcurtiswx)]

Hey all, Thanks for the bug report and the confirmation. If you could provide this bug report with info/links/attachments from the following https://wiki.ubuntu.com/DebuggingSoundProblems then I will get this put in the proper hands. Amazing how buggy PulseAudio still is 'eh. Marking as Incomplete until this information is provided.

[exploder91 (d-cosner)]

I read through the information at the provided link. All of the basic stuff is fine but I can't gat the script to run. I execute the script and nothing happens...

[Brian Curtis (bcurtiswx)]

Actually, I was reading another article and commenting on this bug. This may not exactly be a sound problem, but with the volume manager. Still post the scripts results though, it may help.

[Brian Curtis (bcurtiswx)]

@exploder91, are you typing "bash" before the util program name?

[Tuomas Aavikko (taavikko)]

 http://www.alsa-project.org/db/?f=faec27e18bfe123c0341f53b6ae08ba5cfa1df88

cat /proc/asound/card
card0/ cards
devil@elite:~$ cat /proc/asound/cards
 0 [Intel ]: HDA-Intel - HDA Intel
                      HDA Intel at 0xf7ff8000 irq 22

@exploder,
For getting the alsa.sh do the following
wget http://alsa-project.org/alsa-info.sh -O alsa.sh && bash alsa.sh

[exploder91 (d-cosner)]

Yes, "bash alsa-info.sh". What am I doing wrong? The script does not appear to do anything.

[exploder91 (d-cosner)]

Tried again, success!

http://www.alsa-project.org/db/?f=c29c7bf7a5372b939ae232f368b816b5d4dbe928

[Iain Lane (laney)]

Right, I'm seeing this too. Here's my alsa-info.sh output:

http://www.alsa-project.org/db/?f=eaa7960d4c57f627b767da72f1911cf31bc1ad7f

This bug seems to be throwing up a number of dupes too.

[morryis (morryis)]

alsa-info.txt attached

[FredBezies (fredbezies-deactivatedaccount)]

Seeing it again since last pulse audio update (two days ago or something like this). Very annoying.

[Asif Youssuff (yoasif)]

Also seeing this bug.

http://www.alsa-project.org/db/?f=6292354a0f89b195c4d153962eea0105449a7ca6

[Taima (johan-arvidsson)]

Having the same problem. Alltho, my controls dont change randomly. They're just muted and volume at minimum every time I reboot.

http://www.alsa-project.org/db/?f=ef8e99150dc85b3de3d088a7af7b92f502ae3536

[be4truth (short-unique-name-in-use)]

here too. Ungraded from Intrepid to jaunty. On every reboot sound is muted and level is set to 0.

[Luke Schlather (luke2760)]

Likewise.
http://www.alsa-project.org/db/?f=d00e831c777a7cfde46d7a689e3720fa70e75bf8

[Luke Schlather (luke2760)]

This bug mysteriously seems to have been fixed in a recent patch, but now I have no sound whatsoever on resume from suspend as described in

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/364885

I can't say for certain that these two things happened at the same time (there may have been a bit of lag) but the timing is suspicious.

[Joe (lubuntu-joe)]

##### WORK-AROUND FOR AUDIO PROBLEM #####

1.) Manually adjust the mixer settings to something that is a good default for your audio needs. These settings will be loaded every time you restart your computer.

2.) Change the file permissions for /var/lib/alsa/asound.state to enable read/write access for the group/others (open the folder in Thunar, then right-click the file, select properties, and go to the Permissions tab). If you don't do this, then the next step will give you a permission denied error.

3.) Open up a terminal and enter the command "alsactl store" (without the quotes). This stores your mixer settings in /var/lib/alsa/asound.state for later use.

4.) From The Xubuntu/Xfce menu, go to Settings and open Sessions and Startup. Go to the Application Autostart tab and click the Add button.

5.) Enter the command "alsactl restore" (without the quotes) and the name and description of your choice. This causes the "alsactl restore" command to automatically run when you start your computer. The command restores you mixer settings from /var/lib/alsa/asound.state where you saved them earlier.

[LasseW (lars-wattsgard)]

Hi!

I have a similar problem - but what I experience is that every time I touch Spotify (running under Wine) - the PCM volume is set to "0" and I need to manually set it back again.

Also - when Spotify change track - the level is set to "0" and the next tune cannot be heard...

Are we talking about same thing?
What can I do to provide more/accurate information to you?

[Shaun Mallette (chicagonpg)]

I have this same bug with the random volume decreasing/muting itself on a eeepc 1000.

[BlueLight (bluelight-auroville)]

This bug disappeared with Karmic upgrade on my computer

[Daniel T Chen (crimsun)]

Fixed in Lucid

[be4truth (short-unique-name-in-use)]

This bug got already fix with an update in karmic

[rasjani (jani-mikkonen)]

Seeing the same issue as LasseW described above in freshly installed and up2date Lucid and latest spotify.

[ComLock (comlock)]

Me too: Seeing the same issue as LasseW described above in freshly installed and up2date Lucid and latest spotify.

[ComLock (comlock)]

Hmm, using the ALSA driver instead of the OSS driver works better (thus far).

So following this blindly might not be the way to go :)
http://www.spotify.com/no/help/faq/wine/