Hide Forgot
Created attachment 477938 [details] X.org log from failed attempt to start X server Description of problem: kdm fails to start X server when first booted. Subsequent attempts succeed. Version-Release number of selected component (if applicable): kdm-4.6.0-6.fc15.x86_64 How reproducible: 100% Steps to Reproduce: 1. Install rawhide with KDE, KDM, etc. 2. echo DISPLAYMANAGER=KDE > /etc/sysconfig/desktop 3. Ensure system is configured to start in runlevel 5 4. Reboot Actual results: KDM fails to start X server. System appears to hang at plymouth screen, although it's actually possible to ssh in and kill the kdm process, at which point kdm succeeds in starting X. Expected results: KDM should successfully start X on first try. Additional info: This system was just upgraded from Fedora 14 to rawhide with yum. syslog says: Feb 9 18:04:29 ian kdm[1744]: X server died during startup Feb 9 18:04:29 ian kdm[1744]: X server for display :0 cannot be started, session disabled
Created attachment 477939 [details] X.org log from successful X server start This is the X.org log after ssh'ing into the system as root and running: killall kdm
This does not occur if I remove "rhgb" from the kernel command line (i.e. boot without a plymouth graphical splash screen).
(In reply to comment #2) > This does not occur if I remove "rhgb" from the kernel command line (i.e. > boot without a plymouth graphical splash screen). That's not very clear, is it? If I boot without "rhgb" (but with kernel mode setting), kdm is able to successfully start the X server on the first attempt. Hope that's better.
(In reply to comment #3) > If I boot without "rhgb" (but with kernel mode setting), kdm is able to > successfully start the X server on the first attempt. I spoke too soon. kdm was starting successfully until I turned on MySQL (mysqld). With MySQL enabled, I get the same failure to start the X server. This has got to be some sort of race condition, but I don't know how to debug it further.
Possibly fixed by the latest slew of updates (sample size == 1).
Haven't seen this in a while. Closing.
Can this be re-opened? I'm having the same problem on a fresh install of F18 alpha...
you may have updated to https://admin.fedoraproject.org/updates/FEDORA-2012-16937/plymouth-0.8.8-1.fc18 and see bug #870695 instead?
Ah, yes... downgrading plymouth did indeed fix it. (The symptoms are unhelpfully similar :-(.) Thanks for pointing me to that.