*** This bug is a duplicate of bug 551340 ***
https://bugs.launchpad.net/bugs/551340
This is probably bug #551340, which is fixed in plymouth 0.8.1-3.
Please upgrade and let us know if you still see the problem.
** Changed in: plymouth (Ubuntu)
Assignee: Scott James Remnant (scott) => (u
Installing plymouth-dbgsym locally and running this through gdb gives
the following backtrace:
Loaded symbols for /lib/plymouth/details.so
Core was generated by `/sbin/plymouthd --mode=boot --attach-to-session'.
Program terminated with signal 11, Segmentation fault.
#0 outb (backend=0xefaa70) at
I couldn't get apport to run so early in the boot process but I wrote a
very simple alternative that saves just the core file. Here it is…
** Attachment added: "Core dump from plymouthd"
http://launchpadlibrarian.net/42330277/e091b783-07b2-4ec5-9c26-e77bdef047df.core
--
mountall failure with
See bug #485709 for a background to the mountall problem that (I think)
triggers this.
--
mountall failure with vmhgfs yields plymouth segfault
https://bugs.launchpad.net/bugs/549653
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
There was nothing in /var/crash; I assume that's because the failure
happened so early in the boot process.
--
mountall failure with vmhgfs yields plymouth segfault
https://bugs.launchpad.net/bugs/549653
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
The attached fstab will prevent my VM from booting
** Attachment added: "This is the fstab that won't boot"
http://launchpadlibrarian.net/42301289/fstab
--
mountall failure with vmhgfs yields plymouth segfault
https://bugs.launchpad.net/bugs/549653
You received this bug notification because y
apport information
** Description changed:
Binary package hint: plymouth
I have a upgraded my test Ubuntu desktop VM to Lucid beta 1, but it now
won't boot. One of the main deviations from stock Karmic was addition of
open-vm-tools. The VM was previously installed as Ubuntu 9.04 and
Yes, a segfault in plymouth is certainly a bug. Can you boot the system
using rescue media (i.e., an ISO image), edit the /etc/fstab to comment
out the vmhgfs line, and see whether this allows you to boot?
Once booted into the system, please check whether this plymouth crash
was reported to appor
