Ubuntu
plymouth package

  1. Bug #800701
  2. Comment #8

Comment 8 for bug 800701

Revision history for this message
Steve Langasek (vorlon) wrote : Re: init: plymouth-stop pre-start process terminated with status 1

Do you still see this issue with current oneiric? If so, a couple more things to try:

 - unset the 'GRUB_GFXPAYLOAD_LINUX=1680x1050-24' option in /etc/default/grub and re-run update-grub to see if the error displays
 - run 'apport-collect 800701' so we get full information about your plymouth config. I get hints of it from the plymouth debug log, but I'm not sure which parts are deliberate and which parts might indicate a bug.

In any event, the plymouth debug log indicates a normal exit of plymouth. So *something* is succeeding in calling 'plymouth quit', but then it looks like the plymouth-stop job is being triggered after plymouth has already exited. One possible explanation is that plymouth-stop is being triggered *twice* by two different events: probably 'starting lxdm' + 'stopped rc RUNLEVEL=[2345]', and because the events are far enough apart, plymouth has already exited before the second event happens, preventing upstart from eating the event.

One way to test for this would be for you to add as the first line after 'pre-start script' in /etc/init/plymouth-stop.conf the following:

   echo "$UPSTART_EVENTS" >> /run/what-killed-plymouth.log

then, after booting the system and confirming that you see the error message, attach /run/what-killed-plymouth.log to this bug.