Lucid LiveCD crashes on boot attempt, displays error messages, no input possible

[John King]

Binary package hint: plymouth

When trying to boot from the Lucid Lynx LiveCD daily image (3-10-10) the following messages appear once the boot logo disappears:

(process:355): GLib-WARNING **: getpwuid_r(): failed due to unknown user id (0)
                                   init: uread
ahead-other main process (1264) terminated with status 4
init: ureadahead-other main process (1265) terminated with status 4
init: ureadahead-other main process (1266) terminated with status 4
could not write bytes: Broken pipe
                                                            [ 242.748086] INFO: task plymouthd:355 blocked for more than 120 seconds.
[ 242.748127] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

Also, the Alpha 3 version seemed to hang on the boot screen, but since there was no output I can't say whether or not it was a related incident.

Release: Ubuntu Lucid Lynx (10.04) Daily Build (March 10th, 2010)

[John King (solar95king)]

In case this is a video card issue, my card is the Nvidia GeForce 7000m.

[Steve Langasek (vorlon)]

Thank you for taking the time to report this issue and help to improve Ubuntu.

The blocked process message implies a kernel problem of some kind, probably in the DRM or framebuffer layer. Reassigning to the linux package.

[Ramón Rocha (ramon.rocha)]

I have this exact same behavior from both the 3-10 and 3-12 images

Is this a duplicate of #531027?

[John King (solar95king)]

It very much seems to be a plymouth issue and not a kernel issue; booting both the March 10th Daily CD and the March 17 Daily CD both failed using the graphical boot (but only the March 10 image displayed the console output though), but I could communicate with the kernel with Alt+SysRq. Deleting the quietsplash option in boot options (or, non-graphical boot) however, allowed both to boot perfectly. So I don't think this is a kernel issue.

[John King (kingj-linuxmlsts)]

As of Beta 2, this issue is no longer affecting me; I'm afraid I'm still having (though much less severe) issues involving plymouth though, I've reported a bug here: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/565936