plymouthd assert failure: plymouthd: ./plugin.c:1153: open_input_source: Assertion `backend != ((void *)0)' failed.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Just finishing update via Update Manager
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: plymouth 0.8.2-2ubuntu26
ProcVersionSign
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
AssertionMessage: plymouthd: ./plugin.c:1153: open_input_source: Assertion `backend != ((void *)0)' failed.
Date: Fri Sep 23 02:22:06 2011
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. RC420/RC520/RC720
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 inteldrmfb
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:1153: open_input_source: Assertion `backend != ((void *)0)' failed.
UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago)
UserGroups:
dmi.bios.date: 06/20/2011
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 04FA
dmi.board.
dmi.board.name: RC420/RC520/RC720
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: RC420/RC520/RC720
dmi.product.
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
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 #769525, 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.