plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

Bug Description

-

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: plymouth 0.8.8-0ubuntu15
ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
Uname: Linux 3.13.0-14-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
Date: Sat Mar 22 00:53:44 2014
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2013-08-14 (219 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Hewlett-Packard HP EliteBook 8570w
ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-14-generic root=UUID=e65db810-5bda-4e3d-8115-cb1d835d794a ro quiet splash vt.handoff=7
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-14-generic root=UUID=e65db810-5bda-4e3d-8115-cb1d835d794a ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f5420815430 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7f5420815430) 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_update_status () from /lib/x86_64-linux-gnu/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 trusty on 2014-03-19 (3 days ago)
UserGroups:

dmi.bios.date: 01/31/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68IAV Ver. F.40
dmi.board.name: 176B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 50.1A
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1028C1100:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8570w
dmi.product.version: A1028C1100
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
sunsik (sunsik) 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 #927636, 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.