Please include the result from the following commands on this bug report:
cat /proc/cmdline
cat /proc/fb
ls -l /dev/fb*
>From the output of your splashy process, it looks like your framebuffer is
not setup correctly. What happens when you run:
dfbinfo # as root if possible
You are in trouble if you see something like:
(*) DirectFB/Core: Single Application Core. (2008-04-08 15:15)
(*) Direct/Memcpy: Using Generic 64bit memcpy()
(!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
--> No such file or directory
(!) DirectFB/FBDev: Error opening framebuffer device!
(!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment
variable.
(!) DirectFB/Core: Could not initialize 'system' core!
--> Initialization error!
(#) DirectFBError [DirectFBCreate() failed]: Initialization error!
All in all, splashy should not crash when this happens. We will look into
this.
--
----)(-----
Luis Mondesi
Maestro Debiano
----- START ENCRYPTED BLOCK (Triple-ROT13) ------
Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner
jbeyq.
----- END ENCRYPTED BLOCK (Triple-ROT13) ------
