Damn, got it wrong again. Should be 27/04/10.
--
mountall assertion failure breaks boot process
https://bugs.launchpad.net/bugs/570289
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
sorry, got the date wrong. Should be 27/01/10.
--
mountall assertion failure breaks boot process
https://bugs.launchpad.net/bugs/570289
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
I can confirm that after upgrading today (27/02/10) and rebooting at least 3
times, the error/halt did not occur. The problem seems to have been rectified
in the latest plymouth update.
Thanks guys.
--
mountall assertion failure breaks boot process
https://bugs.launchpad.net/bugs/570289
You rec
I upgraded the plymouth packages and got back to version 2.14 of mountall and
everything runs fine now. I tried re-booting three times and had no problems
(before the bug occurred with every boot).
So I can confirm that this bug is fixed for me.
Thanks a lot, Steve, for getting this fixed so fast
Andreas,
We should have this bug fixed now. You should find after manually
bringing your system up and installing the new plymouth packages that
have just been published that this is resolved for you. Thanks for
taking the time to report this bug - not a pretty bug to have run into
the week of t
This bug was fixed in the package plymouth - 0.8.2-2ubuntu2
---
plymouth (0.8.2-2ubuntu2) lucid; urgency=low
* Don't call ply_boot_client_process_pending_requests on flush, because
ply_event_loop_process_pending_events already calls this for us when the
fd is writable - so c
Sure, I can reproduce it and get you a backtrace.
Unfortunately I never had to create a backtrace on Linux before, so I don't
know how to do it.
Do you have a short list of steps to take or something like a wiki page that
explains how to do it?
--
mountall assertion failure breaks boot process
** Branch linked: lp:ubuntu/plymouth
--
mountall assertion failure breaks boot process
https://bugs.launchpad.net/bugs/570289
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
Hmm; at first blush I thought this was a regression caused by the fix
for bug #559761, but now I'm not so sure, since
ply_event_loop_process_pending_events doesn't appear to call
ply_boot_client_process_pending_request. Andreas, can you help us get a
full backtrace of this mountall crash?
** Chan
** Changed in: plymouth (Ubuntu)
Status: New => Triaged
** Changed in: plymouth (Ubuntu)
Importance: Undecided => High
--
mountall assertion failure breaks boot process
https://bugs.launchpad.net/bugs/570289
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Package changed: mountall (Ubuntu) => plymouth (Ubuntu)
** Changed in: plymouth (Ubuntu)
Assignee: (unassigned) => Steve Langasek (vorlon)
--
mountall assertion failure breaks boot process
https://bugs.launchpad.net/bugs/570289
You received this bug notification because you are a member
11 matches
Mail list logo
