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 eithe
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 fil
** Changed in: plymouth (Ubuntu Lucid)
Status: Fix Released => Fix Committed
--
Latest plymouth update makes lucid stop at startup
https://bugs.launchpad.net/bugs/538292
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
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.
--
Latest plymouth update makes lucid stop at startup
https://bugs.launchpad.net/bugs/538292
You recei
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?
--
Latest plymouth update makes lucid stop at startup
https://bugs.launchpad.net/bugs/538292
You received this bug notification because
> 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 under
On Fri, 2010-03-12 at 23:54 +, 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 err
thx, pablomme/kenden, these instructions above worked as promised. I
already updated mountall and plymouth to -14!
--
Latest plymouth update makes lucid stop at startup
https://bugs.launchpad.net/bugs/538292
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
@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.
--
Latest plymouth update makes lucid stop at startup
https://bugs.launchpad.net/bugs/5
@pablomme
Thanks for the link, those steps worked fine for me.
Back in Lucid now and getting updates now :)
--
Latest plymouth update makes lucid stop at startup
https://bugs.launchpad.net/bugs/538292
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
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 ha
> 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
@Tony: see bug #538298 (a duplicate of this) for one possible solution,
if you have a live CD/USB stick at hand.
--
Latest plymouth update makes lucid stop at startup
https://bugs.launchpad.net/bugs/538292
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
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-
Same here, Plymouth broke my lucid install.
Could you post the details of the manual fix?
Cheers.
--
Latest plymouth update makes lucid stop at startup
https://bugs.launchpad.net/bugs/538292
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
not really fixed until -14 has hit the archive; leaving this open where
people can see it.
** Changed in: plymouth (Ubuntu Lucid)
Status: Fix Released => Fix Committed
** Changed in: plymouth (Ubuntu Lucid)
Milestone: None => ubuntu-10.04-beta-1
** Changed in: plymouth (Ubuntu Lucid)
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
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)
** Changed in: plymouth (Ubuntu)
Status: New => Fix Released
--
Latest plymouth update makes lucid stop at startup
https://bugs.
** Attachment added: "A screenshot."
http://launchpadlibrarian.net/40889638/plymouth-stopeed.boot.png
--
Latest plymouth update makes lucid stop at startup
https://bugs.launchpad.net/bugs/538292
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
19 matches
Mail list logo
