Created attachment 809983 [details] Xorg.0.log from a failed gdm startup attempt About once out of every 10 times or so that I boot my laptop, it does not display the gdm login screen. Instead of doing that, it shows the end of the output from systemd with the standard 'X' cursor over it. If I move the mouse, then the cursor moves, but it just doesn't show the screen. When this occurs, I see this error message pop up in Xorg.0.log: [ 18.971] (EE) intel(0): Failed to submit batch buffer, expect rendering corruption: Invalid argument. When gdm starts up properly, this message does not show up in the log. If I then switch to a different VC, log in as root and do a "service gdm restart" the gdm screen will pop up just fine. The laptop is a Lenovo T520, with this chip according to lspci: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) Relevant package versions: kernel-3.11.3-201.fc19.x86_64 xorg-x11-xinit-1.3.2-8.fc19.x86_64 xorg-x11-server-common-1.14.3-1.fc19.x86_64 xorg-x11-drv-openchrome-0.3.3-1.fc19.x86_64 xorg-x11-drv-nouveau-1.0.9-1.fc19.x86_64 xorg-x11-drv-qxl-0.1.1-0.11.20130514git77a1594.fc19.x86_64 xorg-x11-drv-evdev-2.8.1-2.fc19.x86_64 xorg-x11-server-Xorg-1.14.3-1.fc19.x86_64 xorg-x11-glamor-0.5.0-5.20130401git81aadb8.fc19.x86_64 xorg-x11-drv-wacom-0.22.0-2.fc19.x86_64 xorg-x11-drv-vmmouse-13.0.0-5.fc19.x86_64 xorg-x11-utils-7.5-9.fc19.x86_64 xorg-x11-fonts-Type1-7.5-8.fc19.noarch xorg-x11-drv-intel-2.21.12-2.fc19.x86_64 xorg-x11-drv-fbdev-0.4.3-9.fc19.x86_64 xorg-x11-xkb-utils-7.7-7.fc19.x86_64 xorg-x11-font-utils-7.5-17.fc19.x86_64 xorg-x11-server-utils-7.7-1.fc19.x86_64 xorg-x11-drv-vesa-2.3.2-9.fc19.x86_64 xorg-x11-drv-vmware-13.0.1-1.fc19.x86_64 xorg-x11-drv-mga-1.6.2-7.fc19.x86_64 xorg-x11-drv-modesetting-0.6.0-7.fc19.x86_64 xorg-x11-xauth-1.0.7-3.fc19.x86_64 xorg-x11-drv-synaptics-1.7.1-4.fc19.x86_64 xorg-x11-drv-ati-7.1.0-5.20130408git6e74aacc5.fc19.x86_64 ...though I've seen this happen off and on for several months, so it's likely a long-standing bug. Attaching Xorg.0.log from one of the failed gdm startup attempts.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.