After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 511778 - UI reset state option
UI reset state option
Status: RESOLVED WONTFIX
Product: gnome-applets
Classification: Other
Component: mixer
2.21.x
Other Linux
: Normal enhancement
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-24 12:53 UTC by Pedro Villavicencio
Modified: 2009-02-02 08:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Pedro Villavicencio 2008-01-24 12:53:05 UTC
a wishlist was reported here:

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/95940

per comments:

For restore the mixer settings the users might have to do:

"
1. Delete /var/lib/alsa/asound.state
2. sudo rmmod snd-hda-intel
3. sudo modprobe snd-hda-intel

This should restore your mixer setting to default."

"I think the issue we are finding is that an ALSA asound.state file
dumped by one version of the module causes silent problems with another.
There really should be a way to force a "fresh start" which updates that
file with some simple, universal settings."

"deleting asound.state and rebooting solved my problem"

the issue is that:

"In /etc/init.d/alsa-utils there is a function "sanify_levels_on_card"
which seems useful as a "reset" option. We should expose this in the
mixer UI."

"This problem turned out to be a bad /var/lib/alsa.state. I think we
should expose the "reset" function in /etc/init.d/alsa-utils in the UI
of the mixer. So one can go to the mixer, and press "reset" and have
that function called to sanity-check the state."
Comment 1 Callum McKenzie 2009-02-02 08:51:07 UTC
No. This is a low-level problem and it should be fixed there, not in the UI. There is no place in the UI for magic buttons.