Bug 1017269 - intermittent black screen on boot to gdm
intermittent black screen on boot to gdm
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-10-09 10:14 EDT by Jeff Layton
Modified: 2015-02-17 12:35 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-02-17 12:35:10 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Xorg.0.log from a failed gdm startup attempt (49.10 KB, text/plain)
2013-10-09 10:14 EDT, Jeff Layton
no flags Details

  None (edit)
Description Jeff Layton 2013-10-09 10:14:45 EDT
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:


...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.
Comment 2 Fedora End Of Life 2015-01-09 15:10:36 EST
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.
Comment 3 Fedora End Of Life 2015-02-17 12:35:10 EST
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

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.