[Bug 308211] Re: usplash fails to unlock x on vt8 (ibex)

2008-12-18 Thread Miguel Branco
** Changed in: usplash (Ubuntu)
   Status: New = Invalid

-- 
usplash fails to unlock x on vt8 (ibex)
https://bugs.launchpad.net/bugs/308211
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 308211] Re: usplash fails to unlock x on vt8 (ibex)

2008-12-17 Thread Miguel Branco
Update: I'll eventually invalidate this bug or change its  scope
because:

It happens I could open an xserver on vt8 (was using only startx -- :1
instead of startx -- :1 vt8) so vt8 is definitely not locked as it would
happen with default console=tty8 (and of course there is no ghost
xserver).

So I deduce for the time being the culprit is... the New session
feature from gnome-session manager which is apparently going directly to
vt9, even though vt8 IS released.. Could it be that this was modded
exactly to avoid any conflict with the vt8 usplash (I doubt as the new
session feature works fine if usplash is disabled) ? Or simply that
new session is being misinformed about vt8 being free (it seems now
since ibex that hal is taking care of some X stuff so maybe it is
related - would make sense).

-- 
usplash fails to unlock x on vt8 (ibex)
https://bugs.launchpad.net/bugs/308211
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 308211] Re: usplash fails to unlock x on vt8 (ibex)

2008-12-17 Thread Miguel Branco
Sorry for additional comment:

Bug is also not related to new session.

Simply put, startx -- :1 vt8 opens normally on vt8  but startx -- :1
opens on vt9.

So it seems the system believes vt8 is not available. Hal issue ?

-- 
usplash fails to unlock x on vt8 (ibex)
https://bugs.launchpad.net/bugs/308211
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs