plymouthd crashed with SIGSEGV in script_obj_deref_direct() Crashed right after cold start

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

Bug Description

This crash occurs every time right after cold startup.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
Uname: Linux 3.2.0-7-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Fri Dec 30 10:42:32 2011
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Gigabyte Technology Co., Ltd. 965P-DS4
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-7-generic root=UUID=1b69b4b0-610c-41ac-b95d-b3e7a6cacf08 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-7-generic root=UUID=1b69b4b0-610c-41ac-b95d-b3e7a6cacf08 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fb909994ea0 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7fb909994ea0) 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 precise on 2011-12-18 (15 days ago)
UserGroups:

dmi.bios.date: 06/25/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F12
dmi.board.name: 965P-DS4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd06/25/2009:svnGigabyteTechnologyCo.,Ltd.:pn965P-DS4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn965P-DS4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: 965P-DS4
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Arie (boerties) 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.