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
got this on startup after serious boot problem that i (hopefully fixed by entering a recovery session and reconfiguring X)
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: plymouth 0.8.2-2ubuntu13
ProcVersionSign
Uname: Linux 2.6.38-1-generic i686
Architecture: i386
AssertionMessage: plymouthd: ./plugin.c:697: open_input_source: Assertion `backend != ((void *)0)' failed.
Date: Sun Jan 30 00:46:51 2011
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
MachineType: Compaq Presario 061 NM825AA-ABF CQ2100FR FR920
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcCwd: /
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: plymouth
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/libc.so.6
abort () from /lib/libc.so.6
__assert_fail () from /lib/libc.so.6
?? () from /lib/plymouth/
TextPlymouth: /lib/plymouth/
Title: plymouthd assert failure: plymouthd: ./plugin.c:697: open_input_source: Assertion `backend != ((void *)0)' failed.
UserGroups:
dmi.bios.date: 11/27/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.05
dmi.board.name: CALI
dmi.board.vendor: FOXCONN
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnAmerican
dmi.product.name: NM825AA-ABF CQ2100FR FR920
dmi.product.
dmi.sys.vendor: Compaq Presario 061
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.