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
This is the same as #609921. I submitted this so it would send the support files, if you'd like to look for difference. I'm on an older HP m8100n, though most of the original devices are gone except for mobo, RAM and PSU. You may delete this report when you are finished with the support files.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: plymouth 0.8.2-2ubuntu20
ProcVersionSign
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelMo
Architecture: amd64
AssertionMessage: plymouthd: ./plugin.c:697: open_input_source: Assertion `backend != ((void *)0)' failed.
Date: Fri Mar 25 21:25:56 2011
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110212)
MachineType: HP-Pavilion GC673AA-ABA m8100n
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 () from /lib/x86_
abort () from /lib/x86_
__assert_fail () from /lib/x86_
?? () from /lib/plymouth/
ply_event_
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-03-26 (0 days ago)
UserGroups:
dmi.bios.date: 06/10/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.27
dmi.board.name: Nettle2
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: GC673AA-ABA m8100n
dmi.sys.vendor: HP-Pavilion
BTW, I've been having trouble getting a clean boot from Grub. It hasn't started x, even from the Live CD alpha 1 & 2. I have to boot to failsafe x, then restart x. I haven't had time to collect data for that problem, but maybe you'll see the cause in these support files.