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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
