Bug 742712

Summary:	Text consoles not activated when X server does not start properly.
Product:	[Fedora] Fedora	Reporter:	Jacek Radzikowski <jacek.radzikowski>
Component:	systemd	Assignee:	Lennart Poettering <lpoetter>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	15	CC:	harald, johannbg, kay, lpoetter, metherid, mschmidt, notting, plautrba
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-10-03 07:40:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jacek Radzikowski 2011-10-01 23:24:27 UTC

Description of problem:
The getty* services don't start unless the X server is started properly. This leaves the system accessible only remotely when the X logon screen fails to come up. After the X server is killed, the console switches back to a non-interactive console with boot messages and it is impossible to switch to any other console.
After the prefdm.service is restarted using a remote console and the X logon screen shows up, text consoles become ready to use.


Version-Release number of selected component (if applicable):
systemd-26-9.fc15.x86_64
systemd-units-26-9.fc15.x86_64
systemd-sysv-26-9.fc15.x86_64

How reproducible:
always

Steps to Reproduce:
1. Make X server to time out on statup (don't ask me how, I didn't have to do anything).
2. wait until systemd kills the service
3. Enjoy system not accessible from console
  
Additional info:
Graphical boot is switched off.

Comment 1 Michal Schmidt 2011-10-03 07:28:59 UTC

Which login manager do you use as your prefdm? Is it gdm, kdm, or another?

Comment 2 Jacek Radzikowski 2011-10-03 07:29:41 UTC

kdm

Comment 3 Michal Schmidt 2011-10-03 07:40:10 UTC

The getty services are blocked waiting for plymouth to quit. /etc/X11/prefdm takes care of calling 'plymouth quit' for some login managers, but not for kdm. It expects that kdm will stop plymouth. kdm fails to do that when X has a problem starting.

*** This bug has been marked as a duplicate of bug 736912 ***