plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Bug #854406 reported by Alexander
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

I'm finding it difficult to learn about how to report bugs properly. I hope what I'm doing helps, and if anybody reads this please let me know.
-ame

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: plymouth 0.8.2-2ubuntu25
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-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Sep 18 20:47:11 2011
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MachineType: Hewlett-Packard HP HDX 18 Notebook PC
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic root=UUID=8bffa51a-923c-41f3-ad5a-2cc4a13bdaad ro quiet splash vt.handoff=7
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic root=UUID=8bffa51a-923c-41f3-ad5a-2cc4a13bdaad ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7feefab10ea0 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7feefab10ea0) 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-13 (6 days ago)
UserGroups:

dmi.bios.date: 08/21/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.31
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3610
dmi.board.vendor: Quanta
dmi.board.version: 15.2C
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.31:bd08/21/2009:svnHewlett-Packard:pnHPHDX18NotebookPC:pvrRev1:rvnQuanta:rn3610:rvr15.2C:cvnQuanta:ct10:cvrN/A:
dmi.product.name: HP HDX 18 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

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

affects: ubuntu → plymouth (Ubuntu)
visibility: private → public
tags: removed: need-amd64-retrace
Revision history for this message
Alexander (rhettnaxel) wrote :

error ID OOPS-2089DS46
https://bugs.launchpad.net/bugs/733453
Either I do not have access to this page or it does not exist.
How do I gain access to this page?

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.