Bug 81313 - Phoebe: after firstboot, switching vc causes X to move to vc8
Phoebe: after firstboot, switching vc causes X to move to vc8
Product: Red Hat Public Beta
Classification: Retired
Component: firstboot (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Brent Fox
Depends On:
Blocks: 79579
  Show dependency treegraph
Reported: 2003-01-07 18:20 EST by Chris Kloiber
Modified: 2008-05-01 11:38 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-29 11:02:00 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chris Kloiber 2003-01-07 18:20:42 EST
1. installed Phoebe on IBM x305
2. selections during firstboot:
forward, yes
forward, cancel

3. did NOT login.  switch to vc1.
4.  switch back to vc 7

result:  only an arrow appeared on a black screen in vc7.
gui had moved to vc8.
Comment 1 Marius Andreiana 2003-01-09 14:16:11 EST
It happened to me too, but I couldn't reproduce it again after I started to use
the system.
Comment 2 Brent Fox 2003-01-09 16:18:29 EST
I can reproduce it.  Should be fixed in firstboot-1.0.3-5.  QA, please verify.
Comment 3 Jay Turner 2003-01-10 12:28:15 EST
Looks like things are all taken care of in firstboot-1.0.3-5.
Comment 4 Chris Kloiber 2003-01-13 17:07:05 EST
Wendy Hung at IBM reports that she can still reproduce the problem with
Comment 5 Brent Fox 2003-01-29 11:02:00 EST
I think the problem is that firstboot is sometimes exiting before the X server
has finished dying off.  Then when GDM tries to start it's X server, it appears
that VC7 is already in use, so it starts its server on VC8.

I've added a 1 second sleep that should give the X server time to die before
firstboot exits.  It's not the cleanest way to do it, but it should work.  See
if she can duplicate the problem with firstboot-1.0.4-6

Note You need to log in before you can comment on or make changes to this bug.