[Bug 533054] Re: boot failure because of missing filesystem event

2010-04-13 Thread Scott James Remnant
Since no verification has been received, have given up with this SRU. Anyone affected can upgrade to Lucid soon enough. ** Changed in: mountall (Ubuntu Karmic) Status: Fix Committed => Won't Fix ** Changed in: mountall (Ubuntu Karmic) Assignee: Scott James Remnant (scott) => (unassign

[Bug 533054] Re: boot failure because of missing filesystem event

2010-03-18 Thread Martin Pitt
Accepted mountall into karmic-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Changed in: mountall (Ubuntu Karmic

[Bug 533054] Re: boot failure because of missing filesystem event

2010-03-12 Thread Launchpad Bug Tracker
This bug was fixed in the package mountall - 2.8 --- mountall (2.8) lucid; urgency=low * src/mountall.c: - Flush the D-Bus connection queue before exiting, otherwise we can end up leaving important events like "filesystem" in the memory queue without ever sending it

[Bug 533054] Re: boot failure because of missing filesystem event

2010-03-09 Thread Steve Magoun
Confirmed that the fix in the original bug report fixes the problem in our testing. With that fix, the filesystem event is reliably emitted. -- boot failure because of missing filesystem event https://bugs.launchpad.net/bugs/533054 You received this bug notification because you are a member of Ub

[Bug 533054] Re: boot failure because of missing filesystem event

2010-03-09 Thread Scott James Remnant
No, Roman; that's unrelated - your system is simply waiting for you to press either the S or M key. That's a bug in that it doesn't stop waiting when /opt does appear, but doesn't have anything to do when you press S or M. -- boot failure because of missing filesystem event https://bugs.launchpa

[Bug 533054] Re: boot failure because of missing filesystem event

2010-03-09 Thread Scott James Remnant
** Changed in: mountall (Ubuntu Lucid) Status: Triaged => Fix Committed ** Changed in: mountall (Ubuntu Karmic) Status: Triaged => Fix Committed ** Changed in: mountall (Ubuntu Karmic) Status: Fix Committed => Triaged -- boot failure because of missing filesystem event http

[Bug 533054] Re: boot failure because of missing filesystem event

2010-03-06 Thread Roman Yepishev
Can this bug be the reason why I get "Waiting for /home [SM]" in plymouth during boot that does not let to boot process to continue? Once it has actually booted into gdm w/o /home mounted, once it stuck with "Waiting for /opt [SM]" - /home and /opt are separate partitions. This is happening on a

[Bug 533054] Re: boot failure because of missing filesystem event

2010-03-05 Thread Scott James Remnant
** Changed in: mountall (Ubuntu) Status: New => Triaged ** Changed in: mountall (Ubuntu) Importance: Undecided => High ** Also affects: mountall (Ubuntu Karmic) Importance: Undecided Status: New ** Also affects: mountall (Ubuntu Lucid) Importance: High Status: Triag

[Bug 533054] Re: boot failure because of missing filesystem event

2010-03-05 Thread Steve Magoun
Note that mountall finished mounting the filesystems, so it should have emitted the event: [6.299441] mountall: local finished [6.299646] mountall: fhs mounted [6.299816] mountall: mounted: local 2/2 remote 0/0 virtual 11/11 swap 1/1 [6.299916] event_new: Pending local-filesystems