plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Bug #1286471 reported by Pierre-Olivier Megret
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

Crash occured on login screen. No more information.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: plymouth 0.8.8-0ubuntu15
ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
Uname: Linux 3.13.0-11-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
Date: Thu Feb 27 17:48:20 2014
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2013-12-18 (72 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Hewlett-Packard HP EliteBook 2560p
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=82c7bc41-8a3f-4c9a-b978-48f3e8edc66c ro quiet splash
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-11-generic root=UUID=82c7bc41-8a3f-4c9a-b978-48f3e8edc66c ro quiet splash
SegvAnalysis:
 Segfault happened at: 0x7ff8b38df430 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7ff8b38df430) ok
 source "$0x1" ok
 destination "(%rdi)" (0x4b000000780) 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: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 07/26/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SSU Ver. F.02
dmi.board.name: 162B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 04.1E
dmi.chassis.asset.tag: CNU1362LC4
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68SSUVer.F.02:bd07/26/2011:svnHewlett-Packard:pnHPEliteBook2560p:pvrA0001D02:rvnHewlett-Packard:rn162B:rvrKBCVersion04.1E:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 2560p
dmi.product.version: A0001D02
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Pierre-Olivier Megret (sorrodje) wrote :
information type: Private → Public
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.

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.