Bug 542138

Summary:	kdm console login problem
Product:	[Fedora] Fedora	Reporter:	Neal Becker <ndbecker2>
Component:	kdebase-workspace	Assignee:	Than Ngo <than>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	12	CC:	fedora, fedora, jreznik, kevin, ltinkl, rdieter, smparrish, than
Target Milestone:	---	Keywords:	Reopened, Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-10-20 17:28:41 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:
Bug Depends On:	470004, 572199
Bug Blocks:

Description Neal Becker 2009-11-28 14:34:36 UTC

Description of problem:

This is about kdm.  Doesn't have a BZ entry.

choose console login.  Works fine.  But, even after exiting shell, where is X?  Tried Alt-F1.

Version-Release number of selected component (if applicable):

kdm-4.3.3-7.fc12.1.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Rex Dieter 2009-11-30 12:56:19 UTC

It's a bug in upstart causing this, bug #470004

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

Comment 2 Kevin Kofler 2009-11-30 23:08:38 UTC

Actually, this looks more related to bug 475890 to me.

Comment 3 Kevin Kofler 2009-11-30 23:08:51 UTC

Does changing /etc/kde/kdm/kdmrc as suggested in:
https://bugzilla.redhat.com/attachment.cgi?id=374909
fix your issue?

Comment 4 Neal Becker 2009-12-01 01:52:25 UTC

No, that didn't seem to fix it.  After that change, I noticed vt1 was no longer X, X was on 7 IIRC.

After login to console, and then exit shell, I couldn't find the X server on any vt I tried.
Nothing very informative in /var/log/messages.

Comment 5 Rex Dieter 2009-12-01 13:08:25 UTC

It really is the the upstart bug here.

Comment 6 Rex Dieter 2010-10-20 17:28:41 UTC

ok, upststart is fixed and so is this, for the most part (for me using f13/kde-4.5.2),

Minor problem remains:
* Console login tries vt1, which is empty (is what X normally uses)
(I'm not going to worry too much about this atm, probably requires more plymouth-related love/config)

Switching to v2 (or 3 or 4 or whatever), can login, logout, then X starts back up in ~10 seconds.

Comment 7 Rex Dieter 2010-10-20 17:30:59 UTC

ok,  dropping tty1 from 
ConsoleTTYs=
in kdmrc makes the cosmetic issue go away, though I'm not scared of other side-effects.  I'll test more.

Comment 8 Rex Dieter 2010-10-20 17:45:50 UTC

s/not/now/ :)