Bug 163385 - gnome-display-properties changes not saved
gnome-display-properties changes not saved
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: control-center (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
Depends On:
  Show dependency treegraph
Reported: 2005-07-15 15:04 EDT by Mike Jang
Modified: 2012-06-20 12:00 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 12:00:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mike Jang 2005-07-15 15:04:27 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Description of problem:
Same issue as https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=100532

I notice that gnome-display-properties on other distros (SUSE, Debian) save changes to each individual's home directory, ~/.gconf/%gconf-tree.xml.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Log into GNOME
2.Run gnome-display-properties
3.Change Resolution
4.Click Apply
5.Log out of GNOME
6.Log back into GNOME

Actual Results:  The resolution was changed temporarily, as I wanted to do with gnome-display-properties. However, the next time I log into GNOME, the resolution goes back to the previous settings.
 (changes do work with system-config-properties)

Expected Results:  Resolution should have been changed for the next login.

Additional info:
Comment 1 Jiri Pallich 2012-06-20 12:00:35 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

Note You need to log in before you can comment on or make changes to this bug.