This bug was fixed in the package mountall - 2.14
---
mountall (2.14) lucid; urgency=low
[ Scott James Remnant ]
* Flush updates to Plymouth before emitting Upstart events, in case
the event kills Plymouth. LP: #559761.
* Don't mark a filesystem "nodev" just because it's go
This bug was fixed in the package plymouth - 0.8.2-2ubuntu1
---
plymouth (0.8.2-2ubuntu1) lucid; urgency=low
* src/main.c: if the splash screen isn't up yet, queue message requests
instead of discarding them. LP: #507881.
* src/client/ply-boot-client.c: some replies may be se
I am having a similar issue, but ESC did cancel the disk check and
continued booting Ubuntu.
--
[Lucid] fsck cannot be cancelled in Plymouth
https://bugs.launchpad.net/bugs/562811
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
Chatted with Steve on IRC, and realised why there was a segfault; new
fix applied
** Changed in: mountall (Ubuntu Lucid)
Status: Triaged => Fix Committed
** Changed in: mountall (Ubuntu Lucid)
Assignee: Steve Langasek (vorlon) => Scott James Remnant (scott)
--
[Lucid] fsck cannot be
Your fix was wrong and introduced bugs (and it isn't at all obvious to
me why this would cause a segfault) - I've had to revert it
** Changed in: mountall (Ubuntu Lucid)
Status: Fix Committed => Triaged
--
[Lucid] fsck cannot be cancelled in Plymouth
https://bugs.launchpad.net/bugs/562811
** Branch linked: lp:ubuntu/plymouth
--
[Lucid] fsck cannot be cancelled in Plymouth
https://bugs.launchpad.net/bugs/562811
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:/
** Changed in: plymouth (Ubuntu)
Status: Confirmed => Fix Committed
** Also affects: mountall (Ubuntu Lucid)
Importance: High
Status: Fix Committed
** Also affects: plymouth (Ubuntu Lucid)
Importance: High
Status: Fix Committed
** Changed in: mountall (Ubuntu Lucid)
** Branch linked: lp:ubuntu/mountall
--
[Lucid] fsck cannot be cancelled in Plymouth
https://bugs.launchpad.net/bugs/562811
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:/
Turns out that changes are *also* needed to mountall for this; as soon
as I got libplymouth2 fixed to pass the right responses to the right
callbacks, mountall started segfaulting. ;) Fix committed to bzr.
** Also affects: mountall (Ubuntu)
Importance: Undecided
Status: New
** Changed
ok, after tracing back and forth, I think ti's a plymouth bug after all.
The problem appears to be in ply_boot_client_process_incoming_replies -
whenever it receives data from the server, it calls
ply_list_get_first_node (client->requests_waiting_for_replies) and passes the
returned data to thi
Thanks Steve, bug #501801 is exactly the problem I'm experiencing. I
suppose the other, pre-reboot, symptoms I was experiencing were because
of the errors in / caused by an upgrade (which sounds like another
bug...). I'll look for the update.
--
[Lucid] fsck cannot be cancelled in Plymouth
https:
On Tue, 2010-04-20 at 16:42 +, Steve Langasek wrote:
> I've traced plymouth for this; plymouth is correctly detecting and
> sending the keypress, but mountall is ignoring it. Reassigning to
> mountall.
>
> I suspect a bug in plymouth_answer() regarding plymouth_mnt->error vs.
> plymouth_erro
I've traced plymouth for this; plymouth is correctly detecting and
sending the keypress, but mountall is ignoring it. Reassigning to
mountall.
I suspect a bug in plymouth_answer() regarding plymouth_mnt->error vs.
plymouth_error.
** Package changed: plymouth (Ubuntu) => mountall (Ubuntu)
--
[L
Michael,
That sounds like bug #501801, fixed in mountall 2.13. If you can
recover the system (probably easiest to boot from external media and run
fsck by hand), and install this update, it should fix the problem for
you.
--
[Lucid] fsck cannot be cancelled in Plymouth
https://bugs.launchpad.ne
Upon further inspection it seems that the primary error I'm experiencing
is different from the described bug, although I also experience it
(being unable to cancel fsck with C). I was able to recover my root
partition by booting into a live CD (well, USB-stick) and running fsck
from there, fixing t
I believe this is the same problem I'm experiencing. I have not found a
solution and must reinstall Ubuntu. I notice that before the killer-
reboot there are several other symptoms (perhaps red herrings). The
first one was a XKB error, and now I am having a strange issue where
modal windows (e.g. t
This appears to be reproducible for me here.
** Changed in: plymouth (Ubuntu)
Importance: Undecided => High
** Changed in: plymouth (Ubuntu)
Status: New => Triaged
--
[Lucid] fsck cannot be cancelled in Plymouth
https://bugs.launchpad.net/bugs/562811
You received this bug notification
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/44121697/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/44121698/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/44121699/Dependencies.txt
** A
18 matches
Mail list logo
