Red Hat Bugzilla – Bug 477345
X server locks on startup at runlevel 5 or from cli with startx
Last modified: 2009-04-01 16:38:52 EDT
Xorg appears to lock at the start of gdm or running startx from the command line
I appears the server is started for some period of time as gdm or gnome begins its startup, however after about say 10-15 seconds I get messages on the command line that some component cannot talk to the X server.
Version-Release number of selected component (if applicable):
Locks every time i boot in runlevel 5 or run startx
Steps to Reproduce:
System was in a known good working state from fresh install from DVD ISO onto a Titanium PowerBook G4 550MHZ with 1GB of RAM.
I "Updated" the system via the gnome update panel
Hard lock of X server. Loss of keyboard and mouse (cannot jump back to any console once the X server locks).
I tried both the "ati" driver and the "radeon" driver. The ati driver complained that it went into an infinite loop while the radeon driver failed silently.
Please let me know what I can provide
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf, if available), X server log file (/var/log/Xorg.*.log) and ~/.xsession-errors to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem.
Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report.
Thank you in advance.
Fedora Bugzappers volunteer triage team