Bug 505134 - XRandR KCM (Display settings in System Settings) does not remember settings across sessions
Summary: XRandR KCM (Display settings in System Settings) does not remember settings a...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase-workspace
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-10 19:10 UTC by Paul Smith
Modified: 2009-07-22 12:11 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-07-22 12:11:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Paul Smith 2009-06-10 19:10:17 UTC
When I change the display settings, these do not persist after a logout.

Paul

Comment 1 Rex Dieter 2009-06-12 12:44:39 UTC
How are you changing it?

system-config-display? other?  (The former is preferred, recommended).

Comment 2 Kevin Kofler 2009-06-12 14:03:35 UTC
This has nothing to do with kde-settings (which are our default settings for KDE). If the settings you set in System Settings (is that where you're setting them?) are not getting remembered, that's a kdebase-workspace issue.

Comment 3 Paul Smith 2009-06-12 15:17:57 UTC
Thanks, Rex and Kevin. I did the settings in System Settings, but these settings were not remembered. After Rex's comment, I installed system-config-display, which was not installed, and I configured my display with it. This procedure eliminated the reported problem. Now, I have everything working as expected.

I do not know why system-config-display was not installed by default.

Paul

Comment 4 Steven M. Parrish 2009-07-22 12:11:00 UTC
Thanks for the update.  Going to close this as WORKSFORME.  Please feel free to reopen if the problem returns.

-- 
Steven M. Parrish - KDE Triage Master
                  - PackageKit Triager
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers


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