Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 454640 - X is not configured post install
Summary: X is not configured post install
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-07-09 14:45 UTC by Tethys
Modified: 2008-07-10 14:09 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-07-10 14:09:51 UTC

Attachments (Terms of Use)

Description Tethys 2008-07-09 14:45:54 UTC
Description of problem:
After a fresh F9 install, X is not available. Given that anaconda is
capable of running X during the install, surely it should be capable
of generating a valid X config for use post-install?

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

How reproducible:
Only tried once

Steps to Reproduce:
1. Install F9, after deselecting office productivity apps group
Actual results:
Text only display

Expected results:
Graphical login screen

Additional info:
See bug 454637 for more details

Comment 1 Chris Lumens 2008-07-09 15:01:03 UTC
Some further information would be helpful in debugging this:

- Are X packages (specifically, the ATI driver package) installed?
- Is there an /etc/X11/xorg.conf file, and if so what does it contain?
- Did X attempt to start but failed, or did it go straight into a text login? 
Is there a /var/log/Xorg.*.log file?
- What's in /etc/inittab?  Is it set up to boot into graphical or text?

Comment 2 Tethys 2008-07-09 15:11:19 UTC
xorg-x11-drv-ati-6.8.0-12.fc9.x86_64 is installed. I'm afraid I can't
remember if there was an xorg.conf at the time -- there is now because
I manually hand-crafted one (or rather, modified one that was working
when I had an earlier version of Fedora installed on this box). It looks
like X attempts to start, in that the text console flickers several times,
but never actually starts X. initdefault is 5.

Comment 3 Andy Lindeberg 2008-07-09 17:11:22 UTC
What video card do you use?

Comment 4 Tethys 2008-07-09 17:14:56 UTC
I have both a Radeon X850 GTO and a Radeon X1550. As I said, the
details can be found in bug 454637.

Comment 5 Andy Lindeberg 2008-07-09 18:28:35 UTC
There is nothing we can do at the moment without the rest of the data that Chris
requested. If you can reproduce the problem and provide said data, please reopen
the bug.

Comment 6 Tethys 2008-07-10 10:21:29 UTC
WTF? I've given you the majority of the information requested, and explained
why I don't have the rest. This is a serious bug, one which would prevent 99%
of your users from having a usable system at all, and yet you're closing it
because of insufficient data? I appreciate that this isn't RHEL, and I don't
have any explicit entitlement to support, but still...

I can't reproduce the problem because it's my work machine, and I need it
to do my work. Reinstalling just to try and reproduce the issue really isn't

Comment 7 Chris Lumens 2008-07-10 14:09:51 UTC
It's not going to hit 99% of users, as we haven't seen a flood of bug reports
about this on F9.  Nor have we hit it in our own testing.  If we had, we would
have looked into it to begin with.  This also means we haven't been able to
reproduce it after you filed this bug report.  So, I don't think the impact is
quite as great as you believe.

Now, of the pieces of information I requested, the two most useful were (1) the
X log file, and (2) the X config file written out by anaconda.  These are
important because we need to know if the X driver the config file specified is
the right one, if the loaded driver understands your video card, and so forth. 
Since these sorts of X bugs are highly dependent on the actual hardware (and we
don't have access to every video card ever), we are really stuck if you can't
retest and we can't reproduce.

I appreciate that you can't just nuke your installed system and try again, but
since we're unable to reproduce and I can't remember any other bug reports, I
don't have much choice but to close as INSUFFICIENT_DATA for now.

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