Bug 915522
Summary: | KDE doesn't remember multiple monitor settings | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andrew Hatfield <ahatfiel> |
Component: | kde-workspace | Assignee: | Than Ngo <than> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 18 | CC: | dvratil, jgrulich, jreznik, kevin, ltinkl, mbriza, rdieter, rnovacek, ry, smparrish, than |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-26 01:10:53 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andrew Hatfield
2013-02-25 23:50:18 UTC
(In reply to comment #0) > Description of problem: > KDE does not remember multiple monitor settings set via KDE System Settings > --> Monitors > > Example, 2 Monitors, one which is DVI (primary) and another is VGA. At each > KDE session login, KDE configures the monitors to either Mirror or sets the > VGA monitor on the right (my config is the DVI is "right" and VGA is "left") > > VGA monitor is 20" wide and the DVI is 24" wide > > Version-Release number of selected component (if applicable): > Fedora 18 latest update of KDE 4 > > Each time I set the monitor configuration, I hit Apply as well as Set as > Default - dialogs return positive reponse > > How reproducible: > every KDE session login > > Steps to Reproduce: > 1. Login > 2. Monitor mismatch > 3. > > Actual results: > > > Expected results: > Settings are saved as per user configuration > > Additional info: Also, Gnome works fine - it remembers settings correctly between logins Known issue. Try kscreen. *** This bug has been marked as a duplicate of bug 607180 *** |