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
Unity fails to launch on logon
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: plymouth 0.8.2-2ubuntu18
ProcVersionSign
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelMo
Architecture: amd64
AssertionMessage: plymouthd: ./plugin.c:540: map_to_device: Assertion `head->size > 0' failed.
CrashCounter: 1
Date: Mon Mar 21 20:36:14 2011
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: Apple Inc. MacBook6,1
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:
raise (sig=6) at ../nptl/
abort () at abort.c:92
__assert_fail (assertion=
?? () from /lib/plymouth/
ply_renderer_
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-03-21 (0 days ago)
UserGroups:
dmi.bios.date: 08/27/09
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MB61.88Z.
dmi.board.
dmi.board.name: Mac-F22C8AC8
dmi.board.vendor: Apple Inc.
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAppleInc
dmi.product.name: MacBook6,1
dmi.product.
dmi.sys.vendor: Apple Inc.
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.