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 161287 - gnome-alsamixer does not save any mix properties
gnome-alsamixer does not save any mix properties
Status: RESOLVED FIXED
Product: gnome-alsamixer
Classification: Other
Component: general
unspecified
Other Linux
: Normal major
: ---
Assigned To: Derrick J Houy
Derrick J Houy
: 127443 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-12-14 15:42 UTC by Ryan
Modified: 2010-06-20 22:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch to escape slash with underscore on load & save configurations. (1.57 KB, patch)
2005-02-12 20:52 UTC, Jan Slupski
none Details | Review

Description Ryan 2004-12-14 15:42:56 UTC
My soundcard is a SigmaTel STAC9750/51

My OS is gentoo (but this has happend on FC1,2,3 for me also.

Run gnome-alsamixer, File -> Properties

Uncheck Various Mixer Elements Names.  I now either:

1) close properties dialog then reopen to find all names are checked

2) close properties dialog, quit gnome-alsamixer, restart gnome-alsamixer to
find all names are checked

When I check Mixer Element Names, they dissapear in gnome-alsamixer only until
it is closed and restarted.  Basically all controls are always visible upon
restarting gnome-alsamixer.  This seems to be badly broken for me from long ago,
I'm sorry I've only gotten around to filing a bug till now.
Comment 1 Jan Slupski 2005-02-12 20:52:01 UTC
Created attachment 37417 [details] [review]
Patch to escape slash with underscore on load & save configurations.

This problem occurs whenever soundcard name or slider/toggle names has slash
('/') signi in the name. 

Functions that loads/saves configuration uses slash as special char, so it
cannot be part of name loaded/saved.

Attaching patch that fix this.
Comment 2 Teppo Turtiainen 2005-07-17 09:30:15 UTC
*** Bug 127443 has been marked as a duplicate of this bug. ***
Comment 3 leonik3 2010-06-20 22:01:15 UTC
(In reply to comment #2)
> *** Bug 127443 has been marked as a duplicate of this bug. ***