plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

Bug Description

Crash happened after restarting the computer (after running software update)

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CurrentDmesg:
 [ 23.968801] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
 [ 34.960005] eth0: no IPv6 routers present
Date: Sun Feb 19 19:24:58 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic root=UUID=ec519280-3f66-40aa-98cc-0adc18363654 ro quiet splash vt.handoff=7
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic root=UUID=ec519280-3f66-40aa-98cc-0adc18363654 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f2beb8acea0 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7f2beb8acea0) ok
 source "$0x1" ok
 destination "(%rdi)" (0x7469732069617420) 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/plymouth/script.so
 script_obj_as_custom () from /lib/plymouth/script.so
 script_execute_object () from /lib/plymouth/script.so
 script_lib_plymouth_on_message () from /lib/plymouth/script.so
 ?? () from /lib/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 precise on 2012-02-19 (0 days ago)
UserGroups:

dmi.bios.date: 07/18/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0204
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3A78-T
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0204:bd07/18/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-T:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Ari Torhamo (ari-torhamo) 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 #733453, 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
visibility: 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.