Bug 440389 - Unable to start Xorg
Summary: Unable to start Xorg
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nv
Version: 9
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Dave Airlie
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2008-04-03 10:01 UTC by John Young
Modified: 2018-04-11 08:04 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-07-14 17:28:18 UTC
Type: ---

Attachments (Terms of Use)
last log file when trying to startX (39.98 KB, text/plain)
2008-04-03 10:01 UTC, John Young
no flags Details

Description John Young 2008-04-03 10:01:58 UTC
Description of problem:
Following the update to xorg-x11-server I am unable
to startX

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


How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 John Young 2008-04-03 10:01:58 UTC
Created attachment 300204 [details]
last log file when trying to startX

Comment 2 Adrian "Adi1981" P. 2008-04-03 13:36:33 UTC
Look @ BZ #440263

Comment 3 Matěj Cepl 2008-04-03 15:21:28 UTC
This doesn't look like bug 440263, but I am quite sure there is a dupe, but I
cannot find it now.

Comment 4 John Young 2008-04-03 16:07:15 UTC
I agree BZ 440263 appears to be an exact duplicate of my issue.  It is the same
version of xorg-x11-server and the procedure described for reproduction is
precisely the same - my problem arose initially when trying to boot to graphical


Comment 5 John Young 2008-04-03 17:16:27 UTC
Final comment - the same first aid - reverting to a previous version of Xorg and
Mesa corrects the issue (for the time being)


Comment 6 John Reiser 2008-04-07 02:20:30 UTC
Looks to be the same thing that prevents graphical install from working when
attempted from DVD made by pungi compose of rawhide of 2008-04-05 (Saturday
April 5).  Both i686 and x86_64 fail "Can't open display :1" and fall back to
text mode, right at the beginning of anaconda.

The x86 traceback in X.log is
0: /usr/bin/Xorg(xf86SigHandler+0x79) [0x80bc2e9]
1: [0x130400]
2: /usr/lib/xorg/modules/extensions//libglx.so(__glXScreenInit+0xb1) [0x66fb31]
3: /usr/lib/xorg/modules/extensions//libglx.so [0x66f1d9]
4: /usr/lib/xorg/modules/extensions//libglx.so [0x6695da]
5: /usr/lib/xorg/modules/extensions//libglx.so(GlxExtensionInit+0x162) [0x66e932]
6: /usr/bin/Xorg(InitExtensions+0x8a) [0x80e544a]
7: /usr/bin/Xorg(main+0x2ad) [0x806b1bd]
8: /lib/libc.so.6(__libc_start_main+0xe6) [0x4145d6]
9: /usr/bin/Xorg(FontFileCompleteXLFD+0x221) [0x806a771]

Fatal server error:
Caught signal 11.  Server aborting

The x86_64 traceback in X.log is
0: /usr/bin/Xorg(xf86SigHandler+0x65) [0x479d75]
1: /lib64/libc.so.6 [0x1d9ff80]
2: /usr/lib64/xorg/modules/extensions//libglx.so(__glXScreenInit+0xc8)
3: /usr/lib64/xorg/modules/extensions//libglx.so [0x7f99af22da92]
4: /usr/lib64/xorg/modules/extensions//libglx.so(GlxExtensionInit+0x132)
5: /usr/bin/Xorg(InitExtensions+0x8a) [0x4a1b8a]
6: /usr/bin/Xorg(main+0x2b0) [0x42c6b0]
7: /lib64/libc.so.6(__libc_start_main+0xfa) [0x1d8b40a]
8: /usr/bin/Xorg(FontFileCompleteXLFD+0x281) [0x42bc39]

Fatal server error:
Caught signal 11.  Server aborting

The rpms are:


Comment 7 Bug Zapper 2008-05-14 08:37:04 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:

Comment 8 Bug Zapper 2009-06-09 23:59:11 UTC
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 9 Bug Zapper 2009-07-14 17:28:18 UTC
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.