plymouthd crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
1 Ubuntu quantal 12.10
2 plymouth
3 no crash
4 plymouthd crashed with SIGABRT in raise()
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: plymouth 0.8.4-0ubuntu1
ProcVersionSign
Uname: Linux 3.5.0-9-generic i686
ApportVersion: 2.4-0ubuntu6
Architecture: i386
CurrentDmesg:
[ 30.179676] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[ 30.179685] vboxdrv: Successfully loaded version 4.1.18_Ubuntu (interface 0x00190000).
[ 30.654005] vboxpci: IOMMU not found (not registered)
[ 32.723559] init: plymouth-stop pre-start process (1298) terminated with status 1
[ 300.004034] [Hardware Error]: Machine check events logged
Date: Fri Aug 10 09:22:00 2012
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
ProcCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=
Signal: 6
SourcePackage: plymouth
StacktraceTop:
raise () from /lib/i386-
abort () from /lib/i386-
?? () from /lib/i386-
__assert_fail () from /lib/i386-
ply_event_
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/23/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.00
dmi.board.name: P4VM800
dmi.board.version: 1.00
dmi.modalias: dmi:bvnAmerican
dmi.product.name: P4VM800
dmi.product.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1009238, 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.