Bug 431362 - X doesn't start with laptop lid closed
Summary: X doesn't start with laptop lid closed
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 8
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Adam Jackson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-03 16:31 UTC by Feng Yu
Modified: 2018-04-11 12:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-01-09 07:38:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Xorg log (29.83 KB, text/plain)
2008-02-03 16:31 UTC, Feng Yu
no flags Details

Description Feng Yu 2008-02-03 16:31:45 UTC
Description of problem:

X doesn't start with laptop lid closed. It panic without finding a screen.

Version-Release number of selected component (if applicable):

xorg-x11-server-Xorg-1.3.0.0-40.fc8

How reproducible:
Always

Steps to Reproduce:
1. Power on the computer.
2. Close the display lid.
3. wait a long time (2 min on my T42) until fedora finish booting and start gdm
  
Actual results:
Instead of the gdm welcome window, what I saw is a blue screen which informs me
X failed to start and which tries to guide me to mess up my Xorg.conf.

Expected results:
When I open the laptop lid again, the gdm screen should be displayed.

Additional info:
It looks like a very deep problem in X. 
If the lid is closed, the video chip is shutdown or the video chip will report
the display device(aka screen) is unplugged. On my laptop the case is radeon
driver fails to set the display mode since no display device is connect. Then
our little X server is screwed. 

To avoid this, X need to obtain the ability to start with a dumb screen, and
switch to a new screen on the fly. I've heard that the latest X will support
dynamical device plugging. Maybe or not this new feature will help.

Workaround:
CtrlAltF1
login as root
init 4
init 5

Comment 1 Feng Yu 2008-02-03 16:31:45 UTC
Created attachment 293837 [details]
Xorg log

Comment 4 Bug Zapper 2008-11-26 09:41:00 UTC
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  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 '8'.

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 8'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 8 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2009-01-09 07:38:41 UTC
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 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.