Bug 469042

Summary:	gdm switches from vt1 -> vt7 when X is killed
Product:	[Fedora] Fedora	Reporter:	James Laska <jlaska>
Component:	gdm	Assignee:	jmccann
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	cschalle, jmccann, jturner, mnowak, rstrode, sergey.rudchenko
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-09-23 20:16:47 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 James Laska 2008-10-29 16:55:44 UTC

Description of problem:

When gdm starts after a fresh install, hit <ctrl><alt><Backspace> to restart X.  GDM then switches from running on vt1 to vt7.

Version-Release number of selected component (if applicable):
gdm-2.24.0-11.fc10.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Boot a  fresh install into runlevel 5
2. When GDM starts, type <ctrl><alt><backspace>
  
Actual results:
X on vt1 dies (as expected), and GDM is relaunched on vt7

Expected results:
I would assume it should stay on the same vt (e.g. vt1).

Comment 1 Bug Zapper 2008-11-26 04:26:45 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Michal Nowak 2009-09-09 08:27:28 UTC

Rawhide's the same for me.

Comment 3 Sergey Rudchenko 2009-09-23 20:16:47 UTC


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