reopen 410877 thanks Tim Dijkstra wrote: > On Wed, 14 Feb 2007 07:28:00 +0100 > Michael Biebl <[EMAIL PROTECTED]> wrote: > >> Package: uswsusp >> Version: 0.6~cvs20070202-1 >> Severity: normal >> >> Configuration: splashy in initramfs, uswsusp with splash=y >> >> Upon resume, init-top/splashy is run first, which starts "splashy boot". >> Later, in local-premount/uswsusp, resume is called. >> This tries to start a second instance of splashy ( splash.c:97 >> splashy_open() ). This causes the boot screen to flicker, which looks a >> bit unaesthetically. >> Imo resume should check if splashy already runs and only try to start >> splashy if it isn't running. > > This is impossible. You see, we do not really start a second instance > of splashy, uswsusp is linked to libsplashy and starts the splash > itself. It can't be any different because during suspend/resume > everything is frozen except for the thread that called freeze(). This > means also splashy is frozen and the splash screen wouldn't be visible.
Ok, my explanation was maybe not quite accurate. If I use the default theme it becomes more obvious what happens: On resume, init-top/splashy runs "splashy boot", which brings up the default splash screen. Later, in local-premount/uswsusp, resume thaws the splashy process, which then shows the nice sleeping penguin. After that, the resume process goes along as expected. Maybe init-top/splashy is the right place to fix this. Before starting "splashy boot", you should check if we are starting or resuming and only launch "splashy boot" upon starting. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
