plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Bug #1296436 reported by it.henrik
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

crash after ubuntu booted and I logged in

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: plymouth 0.8.8-0ubuntu15
ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
Date: Sun Mar 23 22:48:38 2014
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2013-04-23 (334 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130422)
MachineType: Hewlett-Packard HP Compaq 6730b (GB987ET#AK8)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=afa32465-25ac-4c88-92bf-24696c4bd6f5 ro quiet splash vt.handoff=7
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=afa32465-25ac-4c88-92bf-24696c4bd6f5 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7ff8974b7430 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7ff8974b7430) ok
 source "$0x1" ok
 destination "(%rdi)" (0x43800000780) 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/x86_64-linux-gnu/plymouth/script.so
 script_obj_as_custom () from /lib/x86_64-linux-gnu/plymouth/script.so
 script_execute_object () from /lib/x86_64-linux-gnu/plymouth/script.so
 script_lib_plymouth_on_boot_progress () from /lib/x86_64-linux-gnu/plymouth/script.so
 ?? () from /lib/x86_64-linux-gnu/libply-splash-core.so.2
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
UpgradeStatus: Upgraded to trusty on 2014-03-01 (22 days ago)
UserGroups:

dmi.bios.date: 09/18/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PDD Ver. F.08
dmi.board.name: 30DD
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 96.18
dmi.chassis.asset.tag: CNU9031TGZ
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDDVer.F.08:bd09/18/2008:svnHewlett-Packard:pnHPCompaq6730b(GB987ET#AK8):pvrF.08:rvnHewlett-Packard:rn30DD:rvrKBCVersion96.18:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6730b (GB987ET#AK8)
dmi.product.version: F.08
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
it.henrik (it-trash) 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 #1223714, 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.

information type: 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.