Bug 660461

Summary: Xserver 1.10 no longer recognizes Plymouth's -nr option and brakes kdm
Product: [Fedora] Fedora Reporter: Martin Kho <rh-bugzilla>
Component: plymouthAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: fedora, kevin, rdieter, rstrode, thomasbelvin, thomasj
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-08 15:42:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Martin Kho 2010-12-06 20:35:13 UTC
Description of problem:

The wiki page 'BetterStartup' [1] states that to: 

"make the X server started by gdm take over the existing vt, mode and framebuffer content

    krh has a patch which adds a -nr ("no root") option which makes the root window keep the framebuffer contents that were around when X started"

But with the release of xserver 1.10 the "-nr" option is no longer recognized. This option is replaced by "-background none", see Peter Hutterer's patch for gdm.

Not only gdm depends on the "-nr" option, also kdm uses it. Changing the "-nr" option in "-background none" doesn't work for kdm.

There is some more that complicates this issue. Plymouth is first started by dracut and taken over by systemd. This has different results:

1. Normal boot -> login screen -> X runs on vt1 (good)
2. Server crash -> "Fatal server error: xf86OpenConsole: VT_WAITACTIVE failed:
Interrupted system call"
3. Boot -> Interrupt Plymouth by pressing the ESC-key ->  login screen -> X
runs on vt7 (not good)
 

[1] http://fedoraproject.org/wiki/Releases/FeatureBetterStartup
[2] http://lists.fedoraproject.org/pipermail/scm-commits/2010-December/527559.html


Version-Release number of selected component (if applicable):
* plymouth-0.8.4-0.20101119.2.fc15.x86_64
* systemd-15-1.fc15.x86_64
* kdm-4.5.85-2.fc15.x86_64 (kde 4.6 beta 2)

How reproducible:
Try booting with kdm as Desktop Manager and see which of the above results will appear :-)

Actual results:
See above

Expected results:
Alway get the kdm log in screen and X running on vt1

Additional info:

Comment 1 Martin Kho 2010-12-07 09:19:42 UTC
Hi,

Some additional observations that might be relevant:

1. When booting the system and the Plymouth Splash screen looks to 'run in one fluid movement', I get the kdm log in screen and everything is fine (X runs on vt1)

2. When booting the system and the Plymouth Splash screen is 'split into two departed screens' (the white 'hourglass' restarts) (this is due to the take over by systemd?) a.) Doing nothing the xserver crashes. b.) Pressing ESC when the 'forked' version of Plymouth starts results in the kdm log in screen, but X runs on vt7 (not good)

Hope this helps

Martin Kho

Comment 2 Martin Kho 2010-12-08 14:08:34 UTC
Hi,

After yesterday's updates [1] this issue seems to be solved. Don't know which package it was. May be xorg-x11-server-1.9.99.1-2.20101201.fc15, initscripts-9.23-2.fc15?


This report can IMHO be closed, thanks.

Martin Kho


[1] http://lists.fedoraproject.org/pipermail/test/2010-December/095924.html