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 340797 - Screen resolution not in GConf schema
Screen resolution not in GConf schema
Status: RESOLVED OBSOLETE
Product: gnome-control-center
Classification: Core
Component: Display
2.14.x
Other All
: Low enhancement
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks: randr-tracker
 
 
Reported: 2006-05-06 05:09 UTC by Mario Carrion
Modified: 2009-02-26 02:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Mario Carrion 2006-05-06 05:09:28 UTC
Please describe the problem:
I don't see this as "real problem", but let me explain it:

Screen Resolution Application sets a GConf key when applying the resolution but
default gconf keys don't contain that key. The only way to get that is to first
run Screen Resolution then clicking Apply.

Steps to reproduce:
1. Use default gconf keys (run a newly created GNOME session)
2. Run gconf-editor, look for /desktop/gnome/screen
3. Key missing

1. Run Screen Resolution, click Apply
2. Run gconf-editor, look for /desktop/gnome/screen/
3. Key appears.

Actual results:
Key is missing.

Expected results:
Key should appear: /desktop/gnome/screen/

Does this happen every time?
First time before clicking Apply

Other information:
Is this set by software design?
Comment 1 Thomas Wood 2007-01-09 16:38:02 UTC
I'm not quite sure we would want to set a default resolution for users, if that is what you are asking? What value do you expect to see in a newly create session?
Comment 2 Mario Carrion 2007-01-09 18:38:29 UTC
I mean to get the resolution used even the "Screen Resolution" application haven't previously used.
Comment 3 Federico Mena Quintero 2009-02-26 02:02:14 UTC
This is obsolete now that we use ~/.config/monitors.xml and the RANDR stack.