On Dec 30, 2008, at 4:42 AM, Tim Richardson wrote:
v 03.13 shows the same behaviour as 0.3.12. That is, splashy doesn't
work with the same error messages.
Also, the /tmp/directfbrc hack fixes it just the same.
I wonder why there was so much confidence that a fix was found. Have
the
developers managed to reproduce the bug yet on their own systems?
Unfortunately, I can't get a virtual machine to show this bug, only my
three real machines.
I'd be more than happy to test any proposed fixes before they are
packaged. I'm trying to follow development via the mailing list, now I
will try to learn IRC.
If the Lenny deep freeze is just around the corner, I suggest using my
mysterious fix (the /tmp/directfbfc fix documented earlier in this bug
report) while we work out what is really happening because at least
then
this bug could be closed.
Hey Tim,
did you try purging Splashy and possible re-installing libdirectfb
directly from Lenny? The problem is this:
when splashy launches it tries to open a font file that's shipped with
splashy itself and it's copied to initramfs under /usr/share/splashy/
themes/default/... (or whatever theme you use)
the C function for splashy that loads the fonts attempts to first load
this font and if it fails, it falls back to NULL which tells directfb
to use whatever default font. this worked well for as long as I can
remember but for some reason it broke in Lenny.
so, I fixed the splashy portion of the code so it always finds the
theme supplied font, and if it does not for whatever reason, it should
fall back to NULL. the C portion of splashy was broken when we
switched paths from /etc/splashy/themes to the new one under /usr.
this is not a problem for people using splashy from initramfs (most
users). only those not using initramfs and using a different partition
for /usr would see an issue (and there is nothing we can do about
this. the end-user would need to resolve this manually in a number of
ways, like changing /etc/splashy/config.xml to point to a partition
that's mounted early enough).
installing Lenny on a fresh VM works well. using splashy on all my
systems also work correctly. I wish somebody else could confirm that
they also have this problem when using 0.3.13.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
