plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Bug #1378668 reported by Robert Avant on 2014-10-08
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Undecided
Unassigned

Bug Description

I am unsure what this bug is or how it is affecting my system.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: plymouth 0.9.0-0ubuntu6
ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
Uname: Linux 3.16.0-20-generic x86_64
ApportVersion: 2.14.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Wed Oct 8 08:03:55 2014
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2014-09-28 (9 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Hewlett-Packard HP Pavilion TS 15 Notebook PC
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-20-generic.efi.signed root=UUID=0b66c77e-1489-4205-ac58-a12830847857 ro recovery nomodeset
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-20-generic.efi.signed root=UUID=0b66c77e-1489-4205-ac58-a12830847857 ro recovery nomodeset
SegvAnalysis:
 Segfault happened at: 0x7fd106fb0600 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7fd106fb0600) ok
 source "$0x1" ok
 destination "(%rdi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL 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.4
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 06/03/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.15
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 216C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 30.25
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.15:bd06/03/2014:svnHewlett-Packard:pnHPPavilionTS15NotebookPC:pvr0881100000305E00000620100:rvnHewlett-Packard:rn216C:rvr30.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion TS 15 Notebook PC
dmi.product.version: 0881100000305E00000620100
dmi.sys.vendor: Hewlett-Packard

Robert Avant (robertj-avant) wrote :

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
Robert Avant (robertj-avant) wrote :

I had not updated before this bug was reported. After updating I do not think I have the problem.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers