It seems that starting splashy later in the boot process caused other problems. After moving splashy script back to init-top, I had not experienced bug #505270, nor #505291
Also, I solved this bug on some of my machines (others resume perfectly) by setting 'early writeout' to 'no' in /etc/uswsusp.conf, so maybe it's not needed to start splashy so late. Best regards, Benoît Laniel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
