Your message dated Sun, 25 May 2008 21:48:12 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: usplash init stop target rework
has caused the Debian Bug report #448979,
regarding usplash: starts too late in the shutdown sequence
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
448979: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448979
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: usplash
Version: 0.5.2-3
Severity: normal
Currently usplash is started again on shutdown by S20sendsigs in
/etc/rc[06].d which is quite late as all the K* scripts will already
have been executed by then (giving a long period of text to look at
first).
Would it perhaps be an idea to move the usplash startup to the usplash
init.d script as it's stop action? Then the usplash init.d link could be
moved from /etc/rc[06].d/K01usplash to /etc/rc[06].d/K02usplash (since
gdm is at prio K01)?
--
David Härdeman
--- End Message ---
--- Begin Message ---
uploaded usplash urgently before doing a cool bike tour,
so doing the bug closures by hand. thanks Petter Reinholdtsen
--
maks
ps the changes below fix aboves bugs
usplash (0.5.19-2) unstable; urgency=low
.
[ Petter Reinholdtsen ]
* usplash: should use omitpit feature to avoid getting killed by
sendsigs
* usplash: starts too late in the shutdown sequence
--- End Message ---
