text renderer does not correctly restore console on 'plymouth quit'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
Confirmed
|
Medium
|
Unassigned | ||
Lucid |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Binary package hint: plymouth
When booting with only the ubuntu-text theme installed, the text consoles are not restored to the expected state on 'plymouth quit': the consoles are all left purple at the end of boot.
Similar problems with the plymouth transition are seen with the details theme when booting into single-user mode. In one instance, the recovery menu comes up with the background on one VT, the menu on a different VT, and the arrow keys let me move around freely in the window instead of letting me choose between the menu options. (The enter key has no effect.)
ProblemType: Bug
Architecture: i386
Date: Mon Mar 29 14:47:31 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Kubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
MachineType: Dell Inc. Inspiron 1520
NonfreeKernelMo
Package: plymouth 0.8.1-1ubuntu3
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANGUAGE=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VGA16 VGA
ProcVersionSign
SourcePackage: plymouth
Uname: Linux 2.6.32-16-generic i686
dmi.bios.date: 07/20/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0UW306
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Inspiron 1520
dmi.sys.vendor: Dell Inc.
other behavior observed:
- if launching plymouth from a terminal with 'start plymouth; start plymouth-splash', switching back to that terminal I find that the Enter key no longer works.
- booting into single user mode with the 'splash' argument added (as in the boot from which this bug was filed) seems to actually work (aside from rcS starting on VT and no VT switch back to tty1 on exit), so it's possible the observed behavior with the details plugin doesn't have the same root cause as the text plugin problem.
- the problem with the background and foreground split across VTs is not reproducible every time, so it looks like there's something racy here.