Bug 445066 - Black screen/disabled keyboard restarting X if xorg.conf file can't be parsed
Black screen/disabled keyboard restarting X if xorg.conf file can't be parsed
Product: Fedora
Classification: Fedora
Component: xorg-x11-server (Show other bugs)
i386 Linux
low Severity low
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-05-03 02:00 EDT by Jonathan Blandford
Modified: 2013-04-02 00:22 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-14 13:39:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Carl Worth 2008-05-03 02:00:19 EDT
Version-Release number:  xorg-x11-server-Xorg-

This is with my i965, in case that's relevant.

Steps to Reproduce (from within X):
1. Introduce a syntax error into /etc/X11/xorg.conf (say, the words
   "syntax error" on the first line)
2. Ctrl-Alt-Backspace
Actual results: Black screen, keyboard seems useless, (can't even switch
to a functioning VT).

Expected results: Should drop me to a functioning VT at least. Bonus points
if it could display the gdm failure text:

gdm-binary[3474]: WARNING: GdmDisplay: display lasted 0.018541 seconds
gdm-binary[3474]: WARNING: GdmLocalDisplayFactory: maximum number of X display
failures reached: check X server log for errors

or perhaps the Xorg.0.log text:

Parse error on line 1 of section (null) in file /etc/X11/xorg.conf
        "Syntax" is not a valid keyword in this section.
(EE) Problem parsing the config file
(EE) Error parsing the config file

But the big bug is that I couldn't fix the system without either
rebooting or logging in from another machine.

Comment 1 Bug Zapper 2008-05-14 06:34:53 EDT
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Comment 3 Bug Zapper 2009-06-09 20:35:57 EDT
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  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 '9'.

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 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
Comment 4 Bug Zapper 2009-07-14 13:39:26 EDT
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.

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.