plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

Bug #1196143 reported by Sander Jonkers
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

Frequent crashes in Ubuntu Saucy with XMir while using Chrome.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: plymouth 0.8.8-0ubuntu7
ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
Uname: Linux 3.9.0-7-generic x86_64
ApportVersion: 2.10.2-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Sat Jun 29 11:30:55 2013
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2013-04-19 (71 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130419)
MachineType: Hewlett-Packard HP ProBook 4530s
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-7-generic root=UUID=caecb19c-bfd2-4d89-a4a1-26ba7014f55a ro quiet splash vt.handoff=7
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-7-generic root=UUID=caecb19c-bfd2-4d89-a4a1-26ba7014f55a ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fd5d7f9fa4c <ply_trigger_add_handler+28>: mov (%rbx),%rdi
 PC (0x7fd5d7f9fa4c) 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 saucy on 2013-06-27 (1 days ago)
UserGroups:

dmi.bios.date: 03/12/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SRR Ver. F.40
dmi.board.name: 167C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 22.24
dmi.chassis.asset.tag: CNU1290ZYV
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68SRRVer.F.40:bd03/12/2013:svnHewlett-Packard:pnHPProBook4530s:pvrA0001D02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.24:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 4530s
dmi.product.version: A0001D02
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Sander Jonkers (jonkers) 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.