Bug 676471

Summary: kdm fails to start X server when first booted.
Product: [Fedora] Fedora Reporter: Ian Pilcher <ipilcher>
Component: kdebase-workspaceAssignee: Than Ngo <than>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: fedora, jreznik, kevin, ltinkl, mwoehlke.floss, rdieter, rnovacek, ry, smparrish, than, thomasj
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-27 00:48:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
X.org log from failed attempt to start X server
none
X.org log from successful X server start none

Description Ian Pilcher 2011-02-10 00:18:14 UTC
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

Comment 1 Ian Pilcher 2011-02-10 00:22:03 UTC
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

Comment 2 Ian Pilcher 2011-02-10 02:12:48 UTC
This does not occur if I remove "rhgb" from the kernel command line (i.e.
boot without a plymouth graphical splash screen).

Comment 3 Ian Pilcher 2011-02-10 02:19:09 UTC
(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.

Comment 4 Ian Pilcher 2011-02-10 02:53:50 UTC
(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.

Comment 5 Ian Pilcher 2011-02-13 02:37:23 UTC
Possibly fixed by the latest slew of updates (sample size == 1).

Comment 6 Ian Pilcher 2011-02-27 00:48:59 UTC
Haven't seen this in a while.  Closing.

Comment 7 Matthew Woehlke 2012-10-31 16:25:10 UTC
Can this be re-opened? I'm having the same problem on a fresh install of F18 alpha...

Comment 8 Rex Dieter 2012-10-31 17:49:31 UTC
you may have updated to 
https://admin.fedoraproject.org/updates/FEDORA-2012-16937/plymouth-0.8.8-1.fc18
and see bug #870695
instead?

Comment 9 Matthew Woehlke 2012-10-31 19:07:54 UTC
Ah, yes... downgrading plymouth did indeed fix it. (The symptoms are unhelpfully similar :-(.)

Thanks for pointing me to that.