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 97847 - Reboot cause Volume levels reset to default
Reboot cause Volume levels reset to default
Status: RESOLVED WONTFIX
Product: gnome-media
Classification: Deprecated
Component: gnome-volume-control
2.0.x
Other Linux
: Normal normal
: ---
Assigned To: Iain
gnome media maintainers
Depends on:
Blocks:
 
 
Reported: 2002-11-06 15:28 UTC by johanw
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0



Description johanw 2002-11-06 15:28:44 UTC
Every time I reboot I must set volume settings, treble, bass etc manually.
The problem is not cosmetic (volume sliders show actual level in use).

How to reproduce:

1. change volume-settings from gnome-volume-control
2. logout and reboot
3. login
4. volume settings is resetted to default


Note: 
In previous version of Gnome (1.4 I think it was, shipped with Mandrake 
8.2) the problem was easily solved by running "gmix -i" at startup but in 
Gnome 2 it do not work (with "gnome-volume-control -i" as stated in --help)
Comment 1 Luis Villa 2002-11-21 23:13:11 UTC

*** This bug has been marked as a duplicate of 94213 ***
Comment 2 Iain 2002-11-22 11:51:57 UTC
Not a duplicate.
This issue is, I'm guessing, that ALSA automatically mutes the
channels, so you need to restore them to their original defaults.

gmix used to be able to do this, but I removed the functionality from
gnome-volume-control, because there are other applications that are
designed for just this: alsactrl I think is one. 
Comment 3 Iain 2002-11-22 11:52:50 UTC
and due to the other utilities being available, I'm not putting this
functionality back into gnome-volume-control
Comment 4 Daniel Eriksson 2003-07-27 12:12:22 UTC
Sorry for continuing discussion on a bug that's been closed for halv a
year, but I can't really see what neither luis nor Iain are talking
about. I have the same problem as Johan. When I've just restarted my
computer I get the following:

[daniel@Datorn daniel]$ gconftool-2 -g
/apps/gnome-volume-control/OSS-Ensoniq_ES1370-1/vol/volume_left
101
[daniel@Datorn daniel]$ gconftool-2 -g
/apps/gnome-volume-control/OSS-Ensoniq_ES1370-1/vol/volume_right
101

...meaning the setting for the volume is at full, which is just what I
did set it to before rebooting. When I start gnome-volume-control I
see that volume is not full, but just about half. I exit
gnome-volume-control and check gconf again:

[daniel@Datorn daniel]$ gconftool-2 -g
/apps/gnome-volume-control/OSS-Ensoniq_ES1370-1/vol/volume_left
64
[daniel@Datorn daniel]$ gconftool-2 -g
/apps/gnome-volume-control/OSS-Ensoniq_ES1370-1/vol/volume_right
64

...meaning volume is now at half. Seems like gnome-volume-control
doesn't load the gconf keys after reboot.

I can't really see the connection between this and muting. The volume
isn't muted, it's just back to default...

I run gnome-media 2.2.1.1 (rawhide rpm) but the problem has been there
for quite a while (could bee since gnome 2 was first installed).