plymouthd assert failure: plymouthd: ply-keyboard.c:384: ply_keyboard_watch_for_input: Assertion `keyboard != ((void *)0)' failed.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: plymouth
Seems to happen at boot when plymouth doesn't displayed (only purple screen of grub), and Ubuntu doesn't start. It started again after using the reset button.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: plymouth 0.8.2-2ubuntu23
ProcVersionSign
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelMo
Architecture: amd64
AssertionMessage: plymouthd: ply-keyboard.c:384: ply_keyboard_
Date: Mon May 16 21:37:29 2011
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7357
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: plymouth
StacktraceTop:
raise () from /lib/x86_
abort () from /lib/x86_
__assert_fail () from /lib/x86_
ply_keyboard_
?? ()
TextPlymouth: /lib/plymouth/
Title: plymouthd assert failure: plymouthd: ply-keyboard.c:384: ply_keyboard_
UpgradeStatus: Upgraded to natty on 2011-03-01 (76 days ago)
UserGroups:
dmi.bios.date: 01/12/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.4
dmi.board.
dmi.board.name: G33M (MS-7357)
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: MS-7357
dmi.product.
dmi.sys.vendor: MICRO-STAR INTERNATIONAL 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 #619021, 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.