Comment 3 for bug 440871

This bug was fixed in the package usplash - 0.5.41

---------------
usplash (0.5.41) karmic; urgency=low

  [ Colin Watson ]
  * Add new options --background and --pidfile, to stop usplash startup
    being racy and to save a second on system shutdown. The pid file is now
    only written after usplash has opened its FIFO and set up the console.
  * Always enable usplash for 9.10 to hide boot messages, since we aren't
    yet ready to make it show up only on relatively slow boots (usplash
    tends to slow down boot on SSD-based systems). We'll revisit this for
    10.04 (LP: #444362).
  * Switch console on normal exit from usplash (i.e. the QUIT command or
    SIGTERM/SIGINT) rather than doing it after usplash exits.
  * On shutdown, wait for X to get the console out of graphics mode before
    starting our own setup.
  * Convert splash-functions to rely on usplash's Upstart job, and avoid
    killing usplash on system shutdown.
  * Redirect init script messages to tty8 if usplash was started during the
    current boot, regardless of the current virtual console (LP: #440871).

  [ Scott James Remnant ]
  * Replace --ignore-sigterm option with proper SIGTERM handling (and SIGINT)
    that causes the main loop to exit just as if it had timed out.
  * Move the shell logic that reads the framebuffer size into the C code to
    save on shell parsing overhead, and avoid the defeating of Upstart
    daemon tracking.
  * Have usplash read the kernel command-line itself and imply -v if
    "quiet" is not present.
  * Merge the usplash and usplash-down Upstart jobs, this neatly means
    that they don't have to check for each other with pidof, and you can
    use "start usplash" and "stop usplash" when you really mean just that.
  * usplash should not be a task (we want "start usplash" to return once
    usplash is running).
  * Fix the standard input flushing function to avoid an infinite loop.

 -- Colin Watson <email address hidden> Fri, 09 Oct 2009 11:34:31 +0100