plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

Bug Description

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: plymouth 0.8.8-0ubuntu5
ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3
Uname: Linux 3.8.0-0-generic x86_64
ApportVersion: 2.8-0ubuntu1
Architecture: amd64
Date: Mon Jan 14 23:41:29 2013
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2012-11-22 (53 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: TOSHIBA Satellite L650
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-0-generic root=UUID=8703e1e6-fdb8-4d28-b52f-7d8eb512c7f0 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=8703e1e6-fdb8-4d28-b52f-7d8eb512c7f0 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f44e6a661d0 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7f44e6a661d0) ok
 source "$0x1" ok
 destination "(%rdi)" (0x307030203000000) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 script_obj_deref_direct () from /lib/x86_64-linux-gnu/plymouth/script.so
 script_obj_as_custom () from /lib/x86_64-linux-gnu/plymouth/script.so
 script_execute_object () from /lib/x86_64-linux-gnu/plymouth/script.so
 script_lib_plymouth_on_update_status () from /lib/x86_64-linux-gnu/plymouth/script.so
 ?? ()
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
UpgradeStatus: Upgraded to raring on 2012-11-26 (49 days ago)
UserGroups:

dmi.bios.date: 11/09/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: 2.40
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvr2.40:bd11/09/2011:svnTOSHIBA:pnSatelliteL650:pvrPSK1JE-018003EP:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Satellite L650
dmi.product.version: PSK1JE-018003EP
dmi.sys.vendor: TOSHIBA

Revision history for this message
Pedroafonsodias (pedroafonsodias) wrote :
description: updated
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 #927636, 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.