plymouthd crashed with SIGSEGV in ply_trigger_add_handler()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
....
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: plymouth 0.8.8-0ubuntu6
ProcVersionSign
Uname: Linux 3.8.0-15-generic x86_64
NonfreeKernelMo
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Sat Mar 30 21:31:50 2013
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2013-02-11 (46 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f1d2bd19e8b <ply_trigger_
PC (0x7f1d2bd19e8b) ok
source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
ply_trigger_
?? ()
ply_event_
ply_event_loop_run () from /lib/x86_
?? ()
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in ply_trigger_
UpgradeStatus: Upgraded to raring on 2013-03-27 (3 days ago)
UserGroups:
dmi.bios.date: 04/23/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.20
dmi.board.name: N68C-S UCC
dmi.board.vendor: ASRock
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: To Be Filled By O.E.M.
dmi.product.
dmi.sys.vendor: To Be Filled By O.E.M.
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 #864430, 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.