ubuntu-x-swat team mailing list archive

[Sean <sean@xxxxxxxxx>]

Confirmation: I did a lucid update this morning (Mar 15th), and this
behaviour has been fixed for me.

Sean

On 15 March 2010 06:01, Steve Langasek <steve.langasek@xxxxxxxxxxxxx>
wrote:

> The majority of users have confirmed that this bug is fixed, so marking
> this again as fixed and unmarking bug #529230 as a duplicate.
>
> ** Changed in: plymouth (Ubuntu)
>       Status: New => Fix Released
>
> --
> Plymouth text-mode splash causes X to crash on first run due to shared tty7
> https://bugs.launchpad.net/bugs/532047
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in X.Org X server: Invalid
> Status in “plymouth” package in Ubuntu: Fix Released
> Status in “xorg-server” package in Ubuntu: Invalid
>
> Bug description:
> Binary package hint: plymouth
>
> Lucid adopted the Plymouth graphical splash service that uses the Kernel
> Mode Setting (KMS) facilities to provide a flicker-free graphical splash
> during start-up. For older video chipsets and drivers (e.g. intel i815) that
> *do not* support KMS plymouth falls back to using a text console (using the
> text plugin). It attaches to tty7 and outputs Linux terminfo control codes
> to draw a colour progress-bar at the bottom of the display.
>
> There is an unfortunate interaction between plymouth and X. X also uses
> tty7. When the X/GDM log-in screen appears for the first time plymouth is
> still running. A script triggers a quit message to the plymouth daemon. It
> seems that plymouth is waiting for either the "2" key or "Enter" key to be
> pressed, whereupon a SIGQUIT (signal 3) is sent to tty7. This causes both
> plymouth *and* X to terminate.
>
> So, if a password contains "2" or the user logs in by pressing "Enter"
> after typing their password, the user experience is that X 'crashes'
> (however, gdb reveals that X receives SIGQUIT).
>
> Some stray plymouth control codes can be witnessed on tty7 if X is stopped
> and tty7 console is on-screen.
>
> Upstart (/sbin/init) then restarts gdm (which launches X) and the second
> session performs correctly.
>
> *** A temporary workaround is to disable the plymouth-splash upstart job
> ***
>
> sudo mv /etc/init/plymouth-splash.conf
> /etc/init/plymouth-splash.conf.disabled
>
>
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/xorg-server/+bug/532047/+subscribe
>

-- 
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.