Ubuntu
plymouth package

plymouth doesn't work well when run from VT7

Bug #496784 reported by Steve Langasek
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Plymouth
Fix Released
Medium
plymouth (Ubuntu)
Fix Released
High
Unassigned
Lucid
Fix Released
High
Unassigned

Bug Description

There are various issues with plymouth running on VT7:

- VT switching doesn't work as you'd expect; it behaves as if plymouth is both on VT1 and VT7, and you can get yourself in a situation where you can't get back

- console messages can appear over top of plymouth

- when starting X, the transition may not work and the screen clears or is corrupted

- when quitting X, the previous framebuffer contents might not be available, or might be mixed in with console messages

See original description
Revision history for this message
Steve Langasek (vorlon) wrote :
Changed in plymouth (Ubuntu):
status: New → Triaged
importance: Undecided → High
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

WFM.

Please provide a video showing the problem

Changed in plymouth (Ubuntu Lucid):
status: Triaged → Incomplete
Revision history for this message
In , Rstrode (rstrode) wrote :

Plymouth's VT handling code isn't really good enough to run plymouth from any vt other than the initial vt.

1) The drm renderer assumes plymouth starts out "active" even before the initial vt switch is finished
2) the console code puts tty0 in PROCESS mode early on. This means we put initial active vt in PROCESS mode, not the one we want to be on. This means we won't get notifications when leaving the right vt, and will get spurious notifications when entering the wrong vt
3) the console code has a state variable that says whether we need to call VT_WAITACTIVE, but it doesn't clear the state variable when the VT is switched behind plymouth's back.

Revision history for this message
In , Scott James Remnant (Canonical) (canonical-scott) wrote :

Notes from brief IRC discussion:

 - ply_console_t is intended to be "the console which has the active vt", but is being used in ways that really mean "plymouth's vt"

 - there isn't a race-free way to always know that the active vt is plymouth's vt

 - rename ply_console_t to ply_vt_t, the operations on it are all the things we want to do to plymouth's VT anyway (VT_PROCESS, set mode, etc.)

 - ply_vt_new (state->default_tty)

 - What about renderers that don't need a VT (x11?)

 - new terminal from vt - for the default case?

 - should ply_console remain just for get_active_vt and set_active_vt which can be done on /dev/tty0 (though they can be done on /dev/tty7 just as easily)

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote : Re: on shutdown from X, splash screen is corrupted, partially overlaid on console messages

Basically plymouth has VT issues and can't run on vt7 after all.

We're trying to get that fixed upstream atm

Changed in plymouth (Ubuntu Lucid):
status: Incomplete → Triaged
summary: - on shutdown from X, splash screen is corrupted, partially overlaid on
- console messages
+ plymouth doesn't work well when run from VT7
Scott James Remnant (Canonical) (canonical-scott)
description: updated
Bug Watch Updater (bug-watch-updater)
Changed in plymouth:
status: Unknown → Confirmed
Revision history for this message
Jordan Bradley (jordan-w-bradley) wrote :

I'm not sure if this is related but on my laptop running 10.04 A1, the console resolution changes but plymouth never shows. There is a mountall error involving plymouth. Plymouth only shows when my machine is shutting down.

Revision history for this message
Jonas Pedersen (jonasped) wrote :

I can confirm the issue jordanwb is reporting. If not related please let me know and I will open a separate bug.

Revision history for this message
Claudio Moretti (flyingstar16) wrote :

jordan and Jonas, there seems to be bug #504052 about it

Revision history for this message
Jonas Pedersen (jonasped) wrote :

Actually I think the bug we are seeing is more bug #502494 - at least this is the bug I see.

Revision history for this message
Id2ndR (id2ndr) wrote :

Removing --attach-to-sessio as describe in bug #502494 allow me to see the plymouth splash instead of "Mountall-could not connect to Plymouth" but plymouth ended just before gdm start.
So I can see text display in the console with then the cursor that was drawn above. At the alpha1 time, plymouth splash remained when the cursor was drawn until the users dropbox appeared.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package plymouth - 0.8.0~-7

---------------
plymouth (0.8.0~-7) lucid; urgency=low

  * Fixed a bug where we couldn't load the script plugin if it were
    compiled without optimisations.
  * Attempt to work around issues with VT switching and fbcon reasserting
    over our output. LP: #496784, #497115.
  * Don't attach to the session for now, this code path doesn't work with
    the current console/VT code. LP: #502494.
 -- Scott James Remnant <email address hidden> Mon, 11 Jan 2010 13:47:36 +0000

Changed in plymouth (Ubuntu Lucid):
status: Triaged → Fix Released
Revision history for this message
Jordan Bradley (jordan-w-bradley) wrote :

Plymouth now works, but if I press a random key on the keyboard, plymouth terminates. Plus I no longer have compositing in gnome, but that's obviously something different.

Revision history for this message
In , Rstrode (rstrode) wrote :

Scott fixed this up a while ago.

Bug Watch Updater (bug-watch-updater)
Changed in plymouth:
importance: Unknown → Medium
status: Confirmed → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in plymouth:
importance: Medium → Unknown
Bug Watch Updater (bug-watch-updater)
Changed in plymouth:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.