Description of problem: Gnome crashes if I have two screens plugged in. Version-Release number of selected component (if applicable): 9.1-1.fc18 How reproducible: always Steps to Reproduce: 1. Shutdown. 2. Unplug the 2nd monitor from the computer. 3. Boot and log into Gnome. 4. Plug in the 2nd monitor. Alternatively, boot with the 2nd monitor plugged in. Actual results: When booting with two screens plugged in, the login manager shows a black screen saying an error has occurred and something about the administrator. When plugging in the monitor after booting, Gnome pops up a black screen saying an error has occurred, and shows a "Log out" button. After logging out Expected results: No crashes. Additional info: I'm opening this bug to get help collecting the information I'd need to get it figured out. I'm not sure where to look. Everything worked until I got the Mesa 9.1 upgrade, so I really think Mesa is at fault. I'm guessing the Radeon driver crashes, and would like some help in figuring out how to send a stack trace.
I tried using KDE, and got this Radeon driver crash right after logging in. I hope the stack trace there might help. https://bugs.kde.org/show_bug.cgi?id=316949
Created attachment 712315 [details] message shown on left screen when booting with both screens attached
Created attachment 712316 [details] entire left screen when booting with both screens plugged in
Created attachment 712317 [details] entire right screen when booting with both screens plugged in
Created attachment 712318 [details] message shown on left screen when plugging left screen after booting
Created attachment 712319 [details] entire left screen when plugging left screen after booting
Created attachment 712320 [details] entire right screen when plugging left screen after booting
Created attachment 715719 [details] /var/log/gdm/:0-greeter.log
Created attachment 715720 [details] /var/log/gdm/:0-greeter-log.1
Created attachment 715721 [details] /var/log/messages The last few thousand lines of /var/log/messages
I dug through the GDM logs and dmesg. These lines seem relevant. radeon: The kernel rejected CS, see dmesg for more information. Mar 24 18:55:59 imapwnu kernel: [ 16.762141] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!
I tried the 3.9 kernel (rc4, I believe) and that didn't help. However, switching to Fedora 19, which brings Gnome 3.8, did make the problem go away. I hope this helps!
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.
Still happening in F20.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.
I haven't run into this in Fedora 19 or Fedora 20, so the logs that I attached are most likely irrelevant now.
Well I can attach logs if I'm told which ones are relevant.
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.
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.