plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

Bug Description

After leaving the system idle for ~20 minutes, it was completely unresponsive. After rebooting, the crash occured immediately after logging in.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Thu Sep 29 18:05:58 2011
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
MachineType: MSI MS-7578
ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-11-generic root=UUID=55782129-5448-4cfa-a7d2-24fc03322b05 ro quiet splash vt.handoff=7
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-11-generic root=UUID=55782129-5448-4cfa-a7d2-24fc03322b05 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f0a31070ea0 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7f0a31070ea0) ok
 source "$0x1" ok
 destination "(%rdi)" (0x726f207465792079) 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 oneiric on 2011-09-04 (25 days ago)
UserGroups:

dmi.bios.date: 03/03/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.7
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: NF750-G55 (MS-7578)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd03/03/2011:svnMSI:pnMS-7578:pvr1.0:rvnMSI:rnNF750-G55(MS-7578):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7578
dmi.product.version: 1.0
dmi.sys.vendor: MSI

Revision history for this message
Jeremy Price (jtull69) 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 Ubuntu 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.