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 144910 - gnome mixer applet does not save audio channel
gnome mixer applet does not save audio channel
Status: RESOLVED DUPLICATE of bug 139374
Product: gnome-applets
Classification: Other
Component: mixer
unspecified
Other Linux
: Normal minor
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-06-24 12:23 UTC by Thomas Maurer
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Thomas Maurer 2004-06-24 12:23:34 UTC
Description of Problem:

The setting of the gnome audio mixer applet does 
not save the channel it
should "access". everytime I restart it's resetted 
to the default
general volume, but I wanna use the PCM-channel. 
that's the problem.

Should be trivial to solve this problem.. It 
worked in 2.4.
Comment 1 Dennis Smit 2004-06-24 19:24:58 UTC
What are you using ? ALSA, OSS, the gstreamer backend ? be a bit more
verbose when reporting bugs :)
Comment 2 Thomas Maurer 2004-06-24 22:43:44 UTC
okey.

I use ALSA (kernel 2.6) with OSS emulation. ehm.. what else do you need to know?

my system: debian testing/unstable (gnome 2.6 from unstable)
-> http://packages.debian.org/unstable/gnome/gnome-applets
package version I currently use. ehm, gstreamer0.8 is installed, but I don't 
know what this does effect the applet-mixer.

If I'm not wrong, it should be a bug of the mixer when saving the settings with 
gconf (the mentioned setting is not saved!). I have no other problems with my 
sound drivers or the kernel.
Comment 3 Dennis Smit 2004-07-09 03:25:09 UTC
I think this has been fixed in CVS, but it's probably difficult for you to
verify right ?
Comment 4 Christian Neumair 2004-07-22 14:26:19 UTC
I'm using the same setup. Obviously it works.

regs,
 Chris

*** This bug has been marked as a duplicate of 139374 ***