plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

Bug Description

Binary package hint: plymouth

appears directly on after gnome login

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: plymouth 0.8.2-2ubuntu22
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Thu Apr 21 21:38:04 2011
DefaultPlymouth: /lib/plymouth/themes/ubuntustudio-logo/ubuntustudio-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: MEDIONPC MS-7616
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=b77d72a8-78a3-4185-a429-e31104594e19 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f0885b89000 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7f0885b89000) ok
 source "$0x1" ok
 destination "(%rdi)" (0x6f20746965726562) 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 natty on 2011-04-20 (6 days ago)
UserGroups:

dmi.bios.date: 04/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A7616IM7.10G
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7616
dmi.board.vendor: MEDIONPC
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: MEDIONPC
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7616IM7.10G:bd04/22/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
dmi.product.name: MS-7616
dmi.product.version: 1.0
dmi.sys.vendor: MEDIONPC

Revision history for this message
coheed froez (michael-kindtner) 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
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.