Hide Forgot
Description of problem: gdm changes the order of the heads from the xorg settings. This is an f20 regression from a working system under f19. Version-Release number of selected component (if applicable): gdm.x86_64 1:3.10.0.1-1.fc20 How reproducible: always. Steps to Reproduce: 1. Boot a multi-head 3 headed system with one small screen on the left (DisplayPort-0) and two large screens in the center and right positions (DisplayPort-1 and DisplayPort-2). 2. Move the mouse across the screens from left to right Actual results: The mouse moves from the displayport-1 to Displayport-0 to displayport-2 monitors in hyperspace fashion. Expected results: mouse motion from dp-0 to dp-1 to dp-2 Additional info: this is not an xorg problem. /var/log/Xorg.0 shows that the dp-0 monitor starts out with offset +0+0. It is in the left-most position in the framebuffer before xdm starts mucking things up. In addition cinnamon has 2 programs that show up in Preferences->Display . Both claim to change around the display order but neither work. The first one comes up with a blank window that claims "could not get screen information". The second shows the mangled monitor positions but doesn't' let one move the monitors around. Luckily xrandr does let you rearrange the monitors. That is a start but not a good system-wide solution. GDM should really keep it's fingers out of the pie and let the Xorg settings stand unless the user explicitly asks for things to be rearranged.
Created attachment 828463 [details] Xorg logfile showing that Xorg got the monitor order right
Bug is still present in F21. Pretty annoying. Spent an hour wondering why xorg.conf was being ignored. I also have a smaller monitor on the left, and two larger monitors in center and right, so this is probably relevant to reproducing. Mine are DVI, DVI and HDMI. Now every user that logs into that computer (it's a "common area" computer) has to re-arrange monitors in GUI config tool after first login. Is there a way to run the monitor config tool for GDM user, at least as a workaround?
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
As mentioned in comment#2, bug is still present in F21... Soon I can check F22 also.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.