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 334052 - Screen refresh rate reverts to highest available
Screen refresh rate reverts to highest available
Status: RESOLVED FIXED
Product: gnome-session
Classification: Core
Component: gnome-session
2.17.x
Other All
: Normal normal
: ---
Assigned To: Session Maintainers
Session Maintainers
: 387854 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-03-09 18:06 UTC by David Bentley
Modified: 2007-03-06 23:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Attachments
xrandr output as requested. (1.38 KB, text/plain)
2006-03-31 18:32 UTC, David Bentley
  Details
gconftool-2 output (12.22 KB, text/plain)
2006-03-31 18:54 UTC, David Bentley
  Details
choose the correct rate (2.29 KB, patch)
2007-02-16 17:01 UTC, Jens Granseuer
committed Details | Review

Description David Bentley 2006-03-09 18:06:39 UTC
Please describe the problem:
After using screen resolution to set the resolution and refresh rate and applying
it all is OK but after you log out and then log back in again the screen
resolution is as expected but the refresh rate has reverted to the highest 
available for the resolution selected not that previously applied.

Steps to reproduce:
1. Change resolution and refresh rate or just refresh rate and apply it
2. Log out 
3. Log back in

Actual results:
When you log back in the refresh rate reverts to the highest available



Expected results:
To remain what it was set at when applied

Does this happen every time?
This happens every time

Other information:
Happens with the current latest version in fedora rawhide pre-FC5 release.
Actual version control-center-2.13.92-2

Reported on http://bugzilla.redhat.com report number 176326
Comment 1 David Bentley 2006-03-14 14:51:23 UTC
Fedora rawhide updated today to version control-center-2.14.0-1 and the bug is still aparent.

Changing to 2.14.x 
Comment 2 Ray Strode [halfline] 2006-03-28 21:03:52 UTC
Hi,

What are the outputs of 

gconftool-2 -R /desktop/gnome/screen 
and
xrandr

?
Comment 3 David Bentley 2006-03-31 18:30:43 UTC
the output of gconftool-2 -R /desktop/gnome/screen is nothing. so I tried
gconftool-2 -R /desktop/gnome and will create an attachment for it together with the output of xrandr
Comment 4 David Bentley 2006-03-31 18:32:00 UTC
Created attachment 62474 [details]
xrandr output as requested.
Comment 5 David Bentley 2006-03-31 18:54:31 UTC
Created attachment 62476 [details]
gconftool-2 output
Comment 6 Bastien Nocera 2007-02-14 13:52:23 UTC
If the output of "gconftool-2 -R /desktop/gnome/screen" is empty, that means the "screen resolution" prefs didn't save anything.
Comment 7 Bastien Nocera 2007-02-15 11:09:03 UTC
Is this still a problem David? Do you see any errors on the command-line when launching gnome-display-properties by hand?
Comment 8 David Bentley 2007-02-15 23:20:39 UTC
The situation is as it has been for some time.

Using gnome-display-properties by hand produces no error output and when you accept the refresh rate change it remains as expected for the current session but if you log out and back in again you are back to the default the top refresh rate offered by gnome-config-display ( in my case that is 60hz when 1280 x 1024 resolution is used an the only other rate offered is 75hz)

conftool-2 -R /desktop/gnome/screen still produces the following output when run after gnome-config-display and not having loged out (changed from 60 to 75 hz refresh rate)

gconftool-2 -R /desktop/gnome/screen
 /desktop/gnome/screen/default:
  /desktop/gnome/screen/default/0:
   rate = 75
   resolution = 1280x1024

but after loging out and back in again it produces no output so the information is not preserved at log out.

current version of gnome 2.16.3 Red Hat,Inc 01/31/2007
vurrent version of gnome-display-properties is 2.16.3
Comment 9 Bastien Nocera 2007-02-15 23:29:03 UTC
I believe that shows a problem with GConf, not with the capplet. If the data is in GConf, it should stay there across sessions. Moving to GConf for analysis.
Comment 10 David Bentley 2007-02-15 23:38:38 UTC
correction after loging out and back in again the output of gconftool-2 is identical to that seen after running gnome-display-properties but the refresh rate is back at the top selection of 60hz.

typo in comment #8 the two instances on gnome-config-display should hve been gnome-display-properties.

So although the info is saved for the user it is not taken any notice of.

Note the options box make default for this computer only is not checked
Comment 11 Jens Granseuer 2007-02-16 17:00:42 UTC
Poor misunderstood GConf didn't do nothing wrong. It's all gnome-session's fault.
Comment 12 Jens Granseuer 2007-02-16 17:01:40 UTC
Created attachment 82687 [details] [review]
choose the correct rate

Here's the proof.
Comment 13 Bastien Nocera 2007-02-16 17:29:38 UTC
(In reply to comment #11)
> Poor misunderstood GConf didn't do nothing wrong. It's all gnome-session's
> fault.

Why is the data in GConf gone after a logout then?

Patch looks good though.
Comment 14 Jens Granseuer 2007-02-16 17:41:43 UTC
Not sure what caused that. Didn't happen for me. In any case there's really no reason why GConf would drop arbitrary settings.
Comment 15 Vincent Untz 2007-02-17 08:27:36 UTC
Thanks, can you commit it?

I'd love to have a small change, though: can you change

get_rate (GConfClient *client, int screen, char *display)

to

get_rate (GConfClient *client, char *display, int screen)
Comment 16 Jens Granseuer 2007-02-17 13:55:05 UTC
Committed with that change.
Comment 17 Bastien Nocera 2007-03-06 23:52:10 UTC
*** Bug 387854 has been marked as a duplicate of this bug. ***