Red Hat Bugzilla – Bug 139590
Sound settings not saved during shutdown
Last modified: 2007-11-30 17:10:54 EST
Description of problem: Sound settings are not save during shutdown. FC3 always start with sound muted or 0 volume. Version-Release number of selected component (if applicable): FC3 How reproducible: Always Steps to Reproduce: 1. Enable sound, set the volume to your liking. 2. Shutdown and restart. 3. Actual results: Sound settings back to 0 volume. Expected results: Sound settings is saved. Additional info: In old OSS days, a couple of lines in /etc/modules.conf do the job of conserving the sound settings. Can the same be used in /etc/modproble.conf?
There already is code in /etc/init.d/halt. What does your /etc/asound.state look like?
Created attachment 107145 [details] /etc/asound.state
Created attachment 107146 [details] /etc/init.d/halt
You've got valid settings in your /etc/asound.state - what happens if you run 'alsactl restore'?
I can only run alsactl restore as root. When I do that, nothing changes with my volume settings.
Odd... looking at your saved state, there certainly are some that are non-zero... everything is still muted in alsamixer? Or can you just not hear anything?
alsactl restore does not mute or set volume to zero at all. Only reboot sets the volume to zero. When that happens, I have to use either alsamixer or aumix to reset my volumes. Is it possible that the saved state somehow got wiped out during shutdown?
The volume always defaults to zero... 'alsactl restore' should work to restore the settings for you ; does that not work instead of alsamixer/etc?
Oh, I understand what you mean now. I'll try that the next time I restart. If that works, do I just add 'alsactl restore' to one of the init script?
No, alsactl should be run automatically when the module is loaded.
Do you work with any window managers (KDE/GNOME), or only on text console? Because window managers realy set volume control to zero during login (especially KDE).
I use GNOME most of the time, but I have tried shutdown and logging into KDE (through gdm) with the same result.
It might be problem of GNOME/KDE. If you use only console (not any X, you have to modify first line of /etc/inittab, you could use "id:3:initdefault:"), work save/restore properly? If you use alsamixer to set volume and reboot, is volume ok (on text console)?
Alright, here is the breakthrough that's needed: When I issue the command: > alsactl store 0 Segmentation fault. There is also an error during shutdown when saving mixer settings. Segmentation fault is also the error message. Any idea what's the problem?
Could you please try new version from devel (1.0.8)?
Did you mean alsa-utils or alsa-lib? I tried alsa-utils since alsactl is in alsa-utils, but I got this error message: # alsactl store 0 alsactl: relocation error: alsactl: symbol snd_ctl_elem_info_is_user, version ALSA_0.9 not definedin file libasound.so.2 with link time reference Done with: alsa-utils-1.0.8-1 alsa-lib-1.0.6-7.FC3
I thought new kernel, alsa-lib and alsa-utils from devel.
Any news?
Problem goes away when I added the mixer applet to gnome, however, issuing the command: [root@localhost ~]# alsactl store 0 alsactl: relocation error: alsactl: symbol snd_ctl_elem_info_is_user, version ALSA_0.9 not defined in file libasound.so.2 with link time reference still gives this error and this error still appears during shutdown. However, it seems like the mixer applet saves its own settings and reload it everytime during startup.
Nevermind, problem fixed when using: alsa-lib-1.0.9rc2-1 alsa-utils-1.0.9rc2-1