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
still can't restart because of the stuck pink image..
ubuntu 11.04 beta1 updated today
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 8 23:55:36 2011
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: Hewlett-Packard HP Pavilion dv5 Notebook PC
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcCwd: /
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-03-26 (14 days ago)
UserGroups:
dmi.bios.date: 07/19/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.07
dmi.board.
dmi.board.name: 3603
dmi.board.vendor: Quanta
dmi.board.version: 02.15
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Pavilion dv5 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
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.