plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

Bug #1098538 reported by Alex Liang
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

ok imeet this,

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: plymouth 0.8.8-0ubuntu5
ProcVersionSignature: Ubuntu 3.8.0-0.2-generic 3.8.0-rc3
Uname: Linux 3.8.0-0-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.8-0ubuntu1
Architecture: amd64
Date: Fri Jan 11 19:53:17 2013
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2012-12-19 (22 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MachineType: TOSHIBA Satellite C805
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-0-generic root=UUID=6c83a3cc-731f-4123-8360-88115fa22dec ro quiet splash vt.handoff=7
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-0-generic root=UUID=6c83a3cc-731f-4123-8360-88115fa22dec ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f1ae65e8e8b <ply_trigger_add_handler+43>: mov (%rbx),%rdi
 PC (0x7f1ae65e8e8b) 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-01-05 (6 days ago)
UserGroups:

dmi.bios.date: 03/01/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.20
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvr1.20:bd03/01/2012:svnTOSHIBA:pnSatelliteC805:pvrPSC6EQ-00M004:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite C805
dmi.product.version: PSC6EQ-00M004
dmi.sys.vendor: TOSHIBA

Revision history for this message
Alex Liang (chinabiue) 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.