plymouthd assert failure: plymouthd: ./plugin.c:540: map_to_device: Assertion `head->size > 0' failed.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: plymouth
I invoked Macslow clock and got an error message.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: plymouth 0.8.2-2ubuntu21
ProcVersionSign
Uname: Linux 2.6.38-
NonfreeKernelMo
Architecture: i386
AssertionMessage: plymouthd: ./plugin.c:540: map_to_device: Assertion `head->size > 0' failed.
Date: Fri Apr 1 15:48:34 2011
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: MSI MS-7267
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: plymouth
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/i386-
abort () from /lib/i386-
__assert_fail () from /lib/i386-
?? () from /lib/plymouth/
TextPlymouth: /lib/plymouth/
Title: plymouthd assert failure: plymouthd: ./plugin.c:540: map_to_device: Assertion `head->size > 0' failed.
UpgradeStatus: Upgraded to natty on 2011-04-01 (0 days ago)
UserGroups:
dmi.bios.date: 08/30/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V17.3
dmi.board.
dmi.board.name: MS-7267
dmi.board.vendor: MSI
dmi.board.version: 4.0
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: MS-7267
dmi.product.
dmi.sys.vendor: MSI
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 #708517, 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.