Package: splashy Version: 0.3.13-5 Severity: important First of all, asumming a framebuffer devices exist before udev is started is a wrong assumption. This was the first bug I found. Moved splashy boot order after udev. Then I saw something new: splashy was complaining about not finding glib which is in /usr/lib while /usr is not mounted.
Looking at the start order I deiscovred I wil then hae many traces before starting it and decided it was not worth the trouble. BTW: also assuming you will have a vga= line in cmdline is totally false as lilo will not let you do this and even if you specifically enter it on the command line, it will discard it. Vga= use another mechanism than command line. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-rc6-git7 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages splashy depends on: ii initramfs-tools 0.93.2 tools for generating an initramfs ii libc6 2.9-12 GNU C Library: Shared libraries ii libdirectfb-1.2-0 1.2.7-2 direct frame buffer graphics - sha ii libgcc1 1:4.4.0-5 GCC support library ii libglib2.0-0 2.20.1-2 The GLib library of C routines ii libmagic1 5.03-1 File type determination library us ii libsplashy1 0.3.13-5 Library to draw splash screen on b ii lsb-base 3.2-22 Linux Standard Base 3.2 init scrip ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime splashy recommends no packages. Versions of packages splashy suggests: ii console-common 0.7.81 basic infrastructure for text cons pn splashy-themes <none> (no description available) ii upstart 0.3.9-2 event-based init daemon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org