Package: usplash
Version: 0.5.8-3
Severity: normal
--- Please enter the report below this line. ---
Hello everyone!
I have been using usplash ever since I installed Debian on my new
computer, and except for minor flaws (that are already tracked) it
worked fine. However, for about 2 weeks my screen just blanks very early
during boot (less then a second after grub's boot menu) and stays blank
until GDM starts X.
I don't know if this issue is really caused by usplash. However, when I
use nosplash as a kernel parameter, everything works just fine (except
for the more "ugly" boot). So I assume this is somehow related to
usplash. Unfortunately, I don't know how to investigate this early stage
of the boot process. Please let me know how to provide additional
information!
For now, the only thing I can do is to describe the symptoms and
implications:
Most interestingly, when doing a splash-enabled boot, it blanks my
screen completely. By this I mean that it puts the screen into some kind
of suspend state. It turns the backlight of my laptop's LCD off! It does
not merely fill the screen with black content.
Other aspects of the boot process don't seem to be affected by this
issue. For instance, I'm using LUKS encrypted partitions so cryptsetup
asks me for their passwords during boot. When usplash still worked, it
used to display appropriate prompts for that. Now, even though I don't
see these prompts they still seem to work. I can enter my passwords and
continue the boot -- all while staring at a blank screen. (To figure out
the right time to enter the passwords I watch the HDD activity indicator
LED on my laptop. Once it stops blinking, it's time to enter a password.)
One more thing I noticed only recently is that all terminals seem to be
broken after a splash-enabled boot, so I cannot change from my Gnome
session to a console using Ctrl-Alt-Fx. All the terminals just show a
blinking "_" in the upper left corner and don't react to input. However,
i can use GDM to create additional Gnome/KDE sessions and switch between
those using Ctrl-Alt-Fx.
Just FYI, this is a sample entry from /boot/grub/menu.lst:
title Debian GNU/Linux, kernel 2.6.24-1-amd64
root (hd0,5)
kernel //vmlinuz-2.6.24-1-amd64
root=/dev/mapper/cryptoroot ro quiet splash vga=792
initrd //initrd.img-2.6.24-1-amd64
Of course, in the original file the kernel line does not contain a
linebreak. I have a separete boot partition. All grub stuff and all
installed Linux kernels come from Debian packages. The only tweaks I did
are in menu.lst itself and they are compliant with update-grub. I also
tried to get rid of the parameter vga=792, but that did not affect this
issue.
As shown below, I have different usplash themes/artworks installed. I
tried to switch between them using the alternatives mechanism. That does
not seem to affect this issue. The one that has been working for me
earlier is usplash-theme-debian. Did not test the others before.
Hope this was the right place to send this report. If not, please let me
know where else I should report this issue! Otherwise, can anyone
suggest a reason why this does not work for me but for others? And maybe
provide a workaround?
Regards,
Michael Riedel
--- System information. ---
Architecture: amd64
Kernel: Linux 2.6.24-1-amd64
Debian Release: lenny/sid
500 testing www.debian-multimedia.org
500 testing security.debian.org
500 testing ftp.nz.debian.org
--- Package information. ---
Depends (Version) | Installed
===================================-+-===========
debconf (>= 0.5) | 1.5.21
OR debconf-2.0 |
initramfs-tools (>= 0.71) | 0.92a
libc6 (>= 2.7-1) | 2.7-10
libusplash0 | 0.5.8-3
usplash-theme-debian | 4
OR usplash-theme |
brdesktop-artwork-usplash | 0.1
debian-edu-artwork-usplash | 0.0.26
libusplash-dev | 0.5.8-3
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
