plymouthd assert failure: plymouthd: ./plugin.c:697: open_input_source: Assertion `backend != ((void *)0)' failed.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: plymouth
After gdm was launched
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: plymouth 0.8.2-2ubuntu22
ProcVersionSign
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
AssertionMessage: plymouthd: ./plugin.c:697: open_input_source: Assertion `backend != ((void *)0)' failed.
Date: Thu Apr 21 09:48:13 2011
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: LENOVO 8927A59
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: plymouth
StacktraceTop:
__kernel_vsyscall ()
raise (sig=6) at ../nptl/
abort () at abort.c:92
__assert_fail (assertion=0xd69ccf "backend != ((void *)0)", file=0xd69cc4 "./plugin.c", line=697, function=0xd6a160 "open_input_
?? () from /lib/plymouth/
TextPlymouth: /lib/plymouth/
Title: plymouthd assert failure: plymouthd: ./plugin.c:697: open_input_source: Assertion `backend != ((void *)0)' failed.
UpgradeStatus: Upgraded to natty on 2011-04-09 (11 days ago)
UserGroups:
dmi.bios.date: 05/08/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 7KETC8WW (2.28 )
dmi.board.name: 8927A59
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 8927A59
dmi.product.
dmi.sys.vendor: LENOVO
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 #710406, 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.