Latest plymouth update makes lucid stop at startup

You need the updated mountall as well
(an upload of plymouth to add Breaks is already in the queue - but couldn't be built at once due to build-depends issues)

I'm sorry, but it seems you upgraded right in the middle of a complex transition. You will need to boot in single user mode or with init=/bin/bash to bypass mountall, remount / read-write by hand, and install the mountall 2.8 package from the archive to recover. (Alternatively, you can use an ISO image as rescue media to boot from, and recover that way.)

The plymouth 0.8.0~-14 package will enforce this upgrade by using Breaks:, but we need the new mountall built on all architectures first before uploading that.

not really fixed until -14 has hit the archive; leaving this open where people can see it.

Same here, Plymouth broke my lucid install.
Could you post the details of the manual fix?

Cheers.

From: http://ubuntuforums.org/showthread.php?t=1428365 :
(Kudos to Rob2687)
Boot using instructions from Steve. The easiest is to use a live CD.

then do:
fdisk -l
(to see your partitions)

sudo mount /dev/sda1 /mnt
(where /dev/sda1 is your boot partition)

sudo chroot /mnt

sudo ln -s /lib/libply-boot-client.so.2.0.0 /lib/libplybootclient.so.2
exit
sudo reboot now

@Tony: see bug #538298 (a duplicate of this) for one possible solution, if you have a live CD/USB stick at hand.

> The plymouth 0.8.0~-14 package will enforce this upgrade by using
> Breaks:, but we need the new mountall built on all architectures
> first before uploading that.

Regarding this, assuming this problem was foreseen and not a human error --which is what I understand from your comment--, is it not possible to build packages without them hitting the mirrors? Transitioning directly from 0.8.0~-12 to 0.8.0~-14 (with an interim, non-public build 0.8.0~-13 in between for technical reasons) would have been the best thing to do, clearly.

plymouth -14 source has been accepted and will build shortly.

mountall 2.8 is published on i386, and is in the process of publishing on amd64. Installing this package is sufficient to fix the problem for any users who have run into this; the plymouth -14 just cleans up to make sure no one else has the problem.

https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/538292/comments/3 describes, in general terms, the process for recovering from this error. It is definitely not recommended to run pre-beta versions of Ubuntu without rescue media available to use for recovery!

@pablomme

Thanks for the link, those steps worked fine for me.
Back in Lucid now and getting updates now :)

@pablomme: Thanks also! I didn't even have plymouth installed and all of a sudden I couldn't reboot! It managed to kill one of my VMs and my main PC also, but at least I've got the main PC back up and running.

thx, pablomme/kenden, these instructions above worked as promised. I already updated mountall and plymouth to -14!

On Fri, 2010-03-12 at 23:54 +0000, pablomme wrote:

> > The plymouth 0.8.0~-14 package will enforce this upgrade by using
> > Breaks:, but we need the new mountall built on all architectures
> > first before uploading that.
>
> Regarding this, assuming this problem was foreseen and not a human error
> --which is what I understand from your comment--, is it not possible to
> build packages without them hitting the mirrors? Transitioning directly
> from 0.8.0~-12 to 0.8.0~-14 (with an interim, non-public build 0.8.0~-13
> in between for technical reasons) would have been the best thing to do,
> clearly.
>
We don't have a way to stop packages hitting the mirrors whilst still
making them available as build dependencies to other packages we're
building.

Scott
--
Scott James Remnant
<email address hidden>

> We don't have a way to stop packages hitting the mirrors whilst still
> making them available as build dependencies to other packages we're
> building.

Ok. Perhaps the ability to flag certain builds as non-public would be something to file a bug report for? (Against Launchpad, I guess?)

I understand this is a rare necessity, and that these things happen only in the alpha/beta stages of a release, but the smoother the process is for testers, the better.

Hm... I had this issue and manually installed the latest mountall. Now the system hangs at the splash screen unless I boot without "splash". What might be wrong?

jyio,

You should file a separate bug report against plymouth for this boot hang issue.

When the hang occurs, please try pressing Alt+F7 or Alt+F1, to see whether you're simply on the wrong VT.

albertjchn: please do not change the status of a bug away from Fix Released without an explanation as to why you believe the original reporter is still having problems.

If you are still experiencing problems yourself, it's quite likely that you had a different bug in the first place and should file a new one - describing the issues you are seeing as accurately as you can.

I tried to update to 10.04 within 9.10 this morning and that did not work except to mess up 9.10.
Removed Ubuntu from under Win.
Downloaded and burned an ISO.

After the install it hangs at the terminal prompt, trying several commands would not work.
Booting to run from the ISO doesn't work either.

Explain with more clarification that "the bug is fixed".