Red Hat Bugzilla – Bug 466599
gnome-display-properties multihead settings don't persist
Last modified: 2014-06-18 05:10:34 EDT
Description of problem: I'm using an ATI video card with dual output. If I disable kernel modesetting in order to use xrandr for display positioning (see bug 466598), I'm able to reorder my displays using gnome-display-properties. However, once I log out, the displays go back to mirroring each other. When I log back in, they remain mirrored. Version-Release number of selected component (if applicable): control-center-2.24.0.1-5.fc10.x86_64 How reproducible: Always Steps to Reproduce: 1. Disable kernel modesetting 2. start gnome-display-properties 3. uncheck "mirror screens" if it's checked 4. move one monitor to the left of the other 5. click apply 6. log out Actual results: The displays will return to their default mode of operation: mirroring each other. Expected results: The settings applied by gnome-display-properties should persist.
can you attach your ~/.config/monitors.xml ?
Created attachment 320111 [details] monitors.xml present during the problem.
I've attached the file that was present at the time. It has three configuration blocks, the first of which refers to outputs which aren't present.
Maybe a duplicate of #163385?
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I don't know what's the problem, but gnome-settings-daemon doesn't start for me as well.
Created attachment 325128 [details] ~/.xsession-errors
Created attachment 325129 [details] /var/log/messages
Now (F10) gnome-settings-daemon starts normally, but gnome-display-properties still does not work with my Intel GM45, while randr does.
Actually for me g-s-d still doesn't run after suspend/resume cycle (gnome-settings-daemon-2.24.1-4.fc10.i386).
Actually for me g-s-d still doesn't run after suspend/resume cycle.
There is nothing to triage here. Switching to ASSIGNED so that developers have responsibility to do whatever they want to do with it.
Do you have acpid running? Someone suggested it should be disabled because gnome-power-manager replaced it completely.
[matej@viklef ~]$ pgrep -f -l acpid 91 kacpid [matej@viklef ~]$ (kacpid is part of kernel)