[Bug 562811] Re: [Lucid] fsck cannot be cancelled in Plymouth
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 got "none" in the device column; this will block the "virtual-filesystems" event which is the one that can't use Plymouth to prompt. LP: #507881. * When cancelling in-progress fsck, don't deference the NULL mount record. LP: #562811. * mountall is missing a very important line of code that increases the udev buffer size; without this it's possible we may miss events during busy periods. LP: #561390. [ Steve Langasek ] * If we're not marking all nodev filesystems as virtual, we need to at least mark our placeholder filesystem entries (type=none && dev=none) this way. -- Steve LangasekSun, 25 Apr 2010 23:36:01 +0100 ** Changed in: mountall (Ubuntu Lucid) Status: Fix Committed => Fix Released -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562811] Re: [Lucid] fsck cannot be cancelled in Plymouth
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 sent out of order because they depend on user input, so pay attention to the message type when picking the handler instead of handing the response to the first handler in the list; without this, cancelling fsck in mountall will never work. LP: #562811. * src/client/ply-boot-client.c: instead of trying to read from the server pipe if there are any outstanding requests, call ply_event_loop_process_pending_events() which already knows whether we can read from the pipe. LP: #559761. * add the pixel display bpp symbols to libplymouth2.symbols with a correct version, so that packages using them don't wind up with overly-strict dependencies on libplymouth2. -- Steve LangasekSun, 25 Apr 2010 16:15:37 +0100 ** Changed in: plymouth (Ubuntu Lucid) Status: Fix Committed => Fix Released -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562811] Re: [Lucid] fsck cannot be cancelled in Plymouth
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562811] Re: [Lucid] fsck cannot be cancelled in Plymouth
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562811] Re: [Lucid] fsck cannot be cancelled in Plymouth
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562811] Re: [Lucid] fsck cannot be cancelled in Plymouth
** 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562811] Re: [Lucid] fsck cannot be cancelled in Plymouth
** 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) Assignee: (unassigned) => Steve Langasek (vorlon) ** Changed in: plymouth (Ubuntu Lucid) Assignee: (unassigned) => Steve Langasek (vorlon) -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562811] Re: [Lucid] fsck cannot be cancelled in Plymouth
** 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562811] Re: [Lucid] fsck cannot be cancelled in Plymouth
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 in: mountall (Ubuntu) Importance: Undecided => High ** Changed in: mountall (Ubuntu) Status: New => Fix Committed -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562811] Re: [Lucid] fsck cannot be cancelled in Plymouth
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 this client requetor. This means that if watch_for_keystroke() is called, and then another request is made that generates a reply, the keystroke handler gets the reply to the *next* request, discards it as "Received odd keys ", and never gets the real keypress when it happens! So I guess our requests_waiting_for_replies list needs to be tagged with the type of reply each one is expecting; the responses will be FIFO within each class, but may be out of order wrt responses of other types. And the reason other keys aren't missed (for 'skip' or 'maintenance shell') is that only during fsck do we send more messages to plymouth after setting a key watch. Scott, given this, I'm not sure why it *wasn't* reproducible for you... am I overlooking something? ** Package changed: mountall (Ubuntu) => plymouth (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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562811] Re: [Lucid] fsck cannot be cancelled in Plymouth
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://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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562811] Re: [Lucid] fsck cannot be cancelled in Plymouth
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_error. > > ** Package changed: plymouth (Ubuntu) => mountall (Ubuntu) > If you've been able to replicate this (I haven't), could you trace the mountall side too? Alternatively let me know how to replicate it :-) Scott -- Scott James Remnant sc...@ubuntu.com ** Changed in: mountall (Ubuntu) Status: Triaged => Confirmed -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562811] Re: [Lucid] fsck cannot be cancelled in Plymouth
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) -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562811] Re: [Lucid] fsck cannot be cancelled in Plymouth
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.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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562811] Re: [Lucid] fsck cannot be cancelled in Plymouth
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 the errors. I don't know why, but fsck was continuously failing while being run in Plymouth. Every time it found an error, it had some error (sorry I don't recall what) and restarted the disk check. Therefore, it would say "Checking disk (n-1/n)" and every time the check failed it would increment n (e.g. 1/2, 2/3, etc...). Should I file a separate bug for this under Plymouth, or does it concern a different project? -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562811] Re: [Lucid] fsck cannot be cancelled in Plymouth
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. the Edit Connections or Reboot windows) display nothing in the form, but just the window border and titlebar. I also noticed that while I could connect to wireless networks, no data would be transmitted (as far as I could tell. Ping tests failed without even sending anything (host unknown error)). These symptoms did not appear except when rebooting resulted in the (seemingly) infinite loop of failed fsck checks. -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562811] Re: [Lucid] fsck cannot be cancelled in Plymouth
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562811] Re: [Lucid] fsck cannot be cancelled in Plymouth
** 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 ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/44121700/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/44121701/Lsusb.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/44121702/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/44121703/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/44121704/ProcModules.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/44121705/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/44121706/UdevLog.txt -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
