usplash breaks VT

[Tormod Volden]

Binary package hint: usplash

After upgrading to 0.5.42 the VT consoles are broken, just a colourful patchwork to be seen.

ProblemType: Bug
Architecture: i386
Date: Sun Oct 11 12:14:26 2009
DistroRelease: Ubuntu 9.10
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Acer, inc. TravelMate 8100
Package: usplash 0.5.42
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-13-generic root=UUID=59b5106f-825d-4931-92d0-b6cd1eee4f49 ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
SourcePackage: usplash
Uname: Linux 2.6.31-13-generic i686
UsplashConf:
 # Usplash configuration file
 # These parameters will only apply after running update-initramfs.

 xres=1680
 yres=1050
XsessionErrors:
 (gnome-settings-daemon:1648): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1648): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:1745): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1732): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
dmi.bios.date: 01/20/06
dmi.bios.vendor: Acer
dmi.bios.version: 3C25
dmi.board.name: Kingfisher
dmi.board.vendor: Acer, Inc.
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: , Inc.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvr3C25:bd01/20/06:svnAcer,inc.:pnTravelMate8100:pvrNotApplicable:rvnAcer,Inc.:rnKingfisher:rvrNotApplicable:cvn,Inc.:ct1:cvrN/A:
dmi.product.name: TravelMate 8100
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer, inc.

[Tormod Volden (tormodvolden)]

Well, now I am not sure any longer what is going on. After downgrading usplash and libusplash0 to 0.5.41 I still have the same problem. And I am sure 0.5.41 worked fine earlier today. Booting without "splash" works fine. The initrd was sure rebuilt between each try.

[Tormod Volden (tormodvolden)]

Note to self: I know 0.5.41 was working because I was working on a console, rebuilding usplash. apt-get source gave me only 0.5.40 because my deb-src was not updated, so I pulled from bzr instead, which gave me 0.5.42 which I patched, built and installed as 0.5.42~tormod. After reboot I saw this error, so I upgraded to the released 0.5.42 which did not help, then I filed this bug.

[anagor (anagor)]

I have the exact same problem with the exact same usplash version.
:)