Usplash doesn't reveal the console when manual intervention is needed, thus leading a user to believe that the computer hangs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
usplash (Ubuntu) |
Fix Released
|
High
|
Steve Langasek | ||
Karmic |
Fix Released
|
High
|
Steve Langasek |
Bug Description
Binary package hint: usplash
I recently ran into a filesystem error on boot, where fsck couldn't automatically fix the problem and the user is expected to manually run fsck.
However, now that usplash is active by default again, the system doesn't even indicate to the user what happened. It just seems to be frozen at the white Ubuntu logo.
I think that this would cause some trouble for new users.
ProblemType: Bug
Architecture: i386
CurrentDmesg: [ 76.432159] eth0: no IPv6 routers present
Date: Sat Oct 10 21:22:03 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Alpha i386 (20091010)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: usplash 0.5.41
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: usplash
Uname: Linux 2.6.31-13-generic i686
UsplashConf:
# Usplash configuration file
# These parameters will only apply after running update-initramfs.
xres=800
yres=600
XsessionErrors:
(gnome-
(gnome-
(nautilus:1439): Eel-CRITICAL **: eel_preferences
(polkit-
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekG
dmi.product.name: VirtualBox
dmi.product.
dmi.sys.vendor: innotek GmbH
Changed in usplash (Ubuntu): | |
assignee: | nobody → Steve Langasek (vorlon) |
importance: | Undecided → High |
milestone: | none → ubuntu-9.10 |
status: | New → Triaged |
tags: | added: regression-potential ubuntu-boot |
I just noticed that usplash _does_ fall back to the console. However there is quite some delay with seemingly no activity.
Also this is still valid for a VirtualBox installation, where I first noticed the problem. Here, too, the Ubuntu logo disappears after a certain amount of time, but there is no visible text.