plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Bug #1058019 reported by Diego Henrique Trentini Gehm on 2012-09-28
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Undecided
Unassigned

Bug Description

Crashes after the start of session (Unity).

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: plymouth 0.8.4-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Fri Sep 28 07:07:50 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntustudio-logo/ubuntustudio-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120830)
MachineType: POSITIVO System Product Name
ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-15-generic root=UUID=336622db-b702-48a2-9812-6919e78fdddf 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=/vmlinuz-3.5.0-15-generic root=UUID=336622db-b702-48a2-9812-6919e78fdddf ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f8c4d7721c0 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7f8c4d7721c0) ok
 source "$0x1" ok
 destination "(%rdi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 script_obj_deref_direct () from /lib/plymouth/script.so
 script_obj_as_custom () from /lib/plymouth/script.so
 script_execute_object () from /lib/plymouth/script.so
 script_lib_plymouth_on_update_status () from /lib/plymouth/script.so
 ?? ()
TextPlymouth: /lib/plymouth/themes/ubuntustudio-text/ubuntustudio-text.plymouth
Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 08/03/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0304
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5GC-MX/CKD/POST/SI
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev x.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: Rev 1.xx
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd08/03/2007:svnPOSITIVO:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5GC-MX/CKD/POST/SI:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx:
dmi.product.name: System Product Name
dmi.product.version: Rev 1.xx
dmi.sys.vendor: POSITIVO

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.

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

Other bug subscribers