Description of problem: Alsamixer does not save its settings when it exits. The settings stay current while the system is running, but they are lost when the system restarts. For example, Speaker volume on my computer is set at 0. When I reset that to 100, my sound is fine, but when I restart, I need to reset the speaker volume again. Version-Release number of selected component (if applicable): alsamixer 1.0.21 How reproducible: Steps to Reproduce: 1. Make a change to one or more settings in alsamixer 2. Restart the system. 3. Actual results: Alsa uses the old settings (the ones that were changed) when the system restarts. Expected results: Alsa should use the new settings when it restarts. Additional info:
Perhaps this may be related to the typo in /lib/alsa/init/default: $ sudo alsaunmute Unknown hardware: "CMI8738-MC6" "CMedia PCI" "" "0x1043" "0x80e2" Hardware is initialized using a guess method /lib/alsa/init/default:75: missing closing brace for format /lib/alsa/init/default:75: error parsing CTL attribute /lib/alsa/init/default:75: invalid rule [Now fix the typo on line 75] $ sudo alsaunmute Unknown hardware: "CMI8738-MC6" "CMedia PCI" "" "0x1043" "0x80e2" Hardware is initialized using a guess method /lib/alsa/init/default:128: missing closing brace for format /lib/alsa/init/default:128: error parsing CTL attribute /lib/alsa/init/default:128: invalid rule [Now fix the typo on line 128]$ sudo alsaunmute Unknown hardware: "CMI8738-MC6" "CMedia PCI" "" "0x1043" "0x80e2" Hardware is initialized using a guess method This appears to be the same, antique bug reported as Bug 500956. Here is a patch that fixes the typos: $ diff -u /lib/alsa/init/default /tmp/default --- /lib/alsa/init/default 2009-09-03 21:05:31.000000000 +1000 +++ /tmp/default 2010-01-02 11:23:43.000000000 +1100 @@ -72,7 +72,7 @@ CTL{name}="PCM Volume",PROGRAM!="__ctl_search", GOTO="pcm0_end" # if master volume control is present, turn PCM volume to max ENV{has_pmaster_vol}=="true",CTL{values}="0dB",RESULT=="0",GOTO="pcm0_end" -ENV{has_pmaster_vol}=="true",CTL{values)="100%",GOTO="pcm0_end" +ENV{has_pmaster_vol}=="true",CTL{values}="100%",GOTO="pcm0_end" # exception - some HDA codecs have shifted dB range CTL{dBmin}=="-34.50dB",CTL{dBmax}=="12.00dB",CTL{values}="0dB",GOTO="pcm0_end" CTL{dBmin}=="-30.00dB",CTL{dBmax}=="0dB",CTL{values}="0dB",GOTO="pcm0_end" @@ -125,7 +125,7 @@ CTL{name}="CD Playback Volume",PROGRAM!="__ctl_search", GOTO="cd0_end" # if master volume control is present, turn CD volume to max ENV{has_pmaster_vol}=="true",CTL{values}="0dB",RESULT=="0",GOTO="cd0_end" -ENV{has_pmaster_vol}=="true",CTL{values)="100%",GOTO="cd0_end" +ENV{has_pmaster_vol}=="true",CTL{values}="100%",GOTO="cd0_end" # exception - some HDA codecs have shifted dB range CTL{dBmin}=="-34.50dB",CTL{dBmax}=="12.00dB",CTL{values}="0dB",GOTO="cd0_end" CTL{dBmin}=="-30.00dB",CTL{dBmax}=="0dB",CTL{values}="0dB",GOTO="cd0_end"
Here is the version installed: $ rpm -q alsa-utils alsa-utils-1.0.21-2.fc12.i686 Happy New Year!
A couple of us have been struggling with this problem for a couple of days now. At this point, it appears to be a problem with opening /etc/asound.state in write mode (during the halt's script run of alsactl store). The strace looks like this: open("/etc/asound.state", O_WRONLY|O_CREAT|O_TRUNC, 0666) = -1 EACCES (Permission denied) write(2, "/sbin/alsactl: save_state:1532: ", 32) = 32 write(2, "Cannot open /etc/asound.state fo"..., 60) = 60 write(2, "\n", 1) = 1 There are complete details (hardware/methodology thus far) here: http://forums.fedoraforum.org/showthread.php?t=248757&page=2 This is on FC13 SS
I have noticed that the problem still exists on my computer - it complains about the fact that it cannot open the file to save the state. However, I managed to manually edit the file to turn my speakers on to full volume, and thankfully it hasn't overwritten that yet, so this bug isn't affecting me too badly at the moment - however, it would still be nice to see this fixed.
This bug still exists in F13 (see bug 588098). Please change the Version to 13, it might get more attention that way.
See bug 637291. The file /etc/asound.state is created with the wrong SELinux context. Run "restorecon -v /etc/asound.state" as root to fix it.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.