mountall assert failure: mountall.c:1296: Not reached assertion failed in mounted

[rwallick]

Binary package hint: mountall

Upon boot, I am receiving a message that mountall can not mount a device called "Plymouth" which I am assuming is the graphical boot animation/logger. This appears to be what is initiating the crash. This is reproducible on my laptop; it occurs on every boot. My laptop is a vanilla Acer Aspire 6920G.

I will keep my system as configured for the next few weeks so, if you find need, I can make it available. Please let me know if there are any specific measures you would like me to take.

Thanks for all the great work being done!

rwallick@Hairy:~$ lsb_release -rd
Description: Ubuntu lucid (development branch)
Release: 10.04

apt-cache policy mountall
mountall:
  Installed: 2.3
  Candidate: 2.3
  Version table:
 *** 2.3 0
        500 http://ubuntu.osuosl.org lucid/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
AssertionMessage: mountall.c:1296: Not reached assertion failed in mounted
CrashCounter: 1
Date: Tue Jan 12 07:11:50 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /sbin/mountall
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
NonfreeKernelModules: nvidia
Package: mountall 2.3
ProcAttrCurrent: unconfined (enforce)
ProcCmdline: mountall --daemon
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
Signal: 6
SourcePackage: mountall
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /sbin/mountall
 ?? () from /sbin/mountall
Tags: lucid
Title: mountall assert failure: mountall.c:1296: Not reached assertion failed in mounted
Uname: Linux 2.6.32-10-generic i686
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #505748, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.