plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

Bug #1162294 reported by Andy Hill
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

reboot after upgrade

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: plymouth 0.8.8-0ubuntu6
ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
Uname: Linux 3.8.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Sat Mar 30 17:20:39 2013
DefaultPlymouth: /lib/plymouth/themes/mythbuntu-logo/mythbuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2012-09-29 (182 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MachineType: HP-Pavilion GM431AA-ABU a6150.uk
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-15-generic root=UUID=742321cf-dd1d-45b7-866d-526180a4376d ro crashkernel=384M-2G:64M,2G-:128M quiet splash
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-15-generic root=UUID=742321cf-dd1d-45b7-866d-526180a4376d ro crashkernel=384M-2G:64M,2G-:128M quiet splash
SegvAnalysis:
 Segfault happened at: 0x7fdce5a88e8b <ply_trigger_add_handler+43>: mov (%rbx),%rdi
 PC (0x7fdce5a88e8b) 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_add_handler () from /lib/x86_64-linux-gnu/libply.so.2
 ?? ()
 ply_event_loop_process_pending_events () from /lib/x86_64-linux-gnu/libply.so.2
 ply_event_loop_run () from /lib/x86_64-linux-gnu/libply.so.2
 ?? ()
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_trigger_add_handler()
UpgradeStatus: Upgraded to raring on 2013-03-07 (22 days ago)
UserGroups: mythtv
dmi.bios.date: 10/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.13
dmi.board.name: Berkeley
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd10/24/2007:svnHP-Pavilion:pnGM431AA-ABUa6150.uk:pvr:rvnASUSTeKComputerINC.:rnBerkeley:rvr1.xx:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: GM431AA-ABU a6150.uk
dmi.sys.vendor: HP-Pavilion

Revision history for this message
Andy Hill (neoshades) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.