Comment 22 for bug 504224

On Sat, Jul 30, 2011 at 03:21:33PM -0000, Kat Amsterdam wrote:
> Proof of this bug in a screenshot. I have had my ubuntu customer in a
> panic now twice due to this matter. It happens when the machine has been
> turned off for the night. The next day he starts the machine (the nas
> runs 24/7 but goes into sleep mode), but the nas is still sleeping, so
> it doesn't react right away to the request to mount. The system hangs
> with the message in the screenshot.

This is not the same bug as originally described, despite having
superficially similar symptoms. Please file a separate bug report for the
problem you're experiencing.

For me, the obvious first question is: why is plymouth exiting before
mountall has finished? Nothing in the /etc/init/plymouth-stop.conf job
should stop plymouth until the filesystem mounting is finished. So even if
the mount triggers too early the first time around, plymouth should still be
waiting for mountall-net to trigger and retry the network mount (and you
should never see the error message in normal operation).

The second question is why dbus is being killed with SIGTERM.

Is this screenshot taken after pressing Ctrl+Alt+Delete on the console?

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>