plymouthd crashed with SIGSEGV in ply_trigger_add_handler()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This samke bug occrs in Ubuntu 13.04 - sorry I lost the details. However I do get several multiple error in a row often times. In this the environment was Ubuntu. More like this in Gnome. Fewer in KDE.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: plymouth 0.8.8-0ubuntu6
Uname: Linux 3.6.11-
NonfreeKernelMo
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Wed Feb 13 23:54:44 2013
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2013-01-24 (20 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD3
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: 0x7f43a4ac5e8b <ply_trigger_
PC (0x7f43a4ac5e8b) 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-01-26 (18 days ago)
UserGroups:
dmi.bios.date: 05/30/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F8
dmi.board.name: GA-990FXA-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: GA-990FXA-UD3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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.