plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Bug #1652360 reported by Fenyvesi Attila
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I got this bug right after starting Xubuntu 16. 04. and logging in.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: plymouth 0.9.2-3ubuntu13.1
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Fri Dec 23 18:49:11 2016
DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2014-12-04 (749 days ago)
InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Hewlett-Packard HP ProBook 6470b
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic root=UUID=a65b2c0c-545b-4b5e-90fa-f32a8319282a ro quiet splash acpi_backlight=vendor vt.handoff=7
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic root=UUID=a65b2c0c-545b-4b5e-90fa-f32a8319282a ro quiet splash acpi_backlight=vendor vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f8fb5f40630 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7f8fb5f40630) 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 /usr/lib/x86_64-linux-gnu/plymouth/script.so
 script_obj_as_custom () from /usr/lib/x86_64-linux-gnu/plymouth/script.so
 script_execute_object () from /usr/lib/x86_64-linux-gnu/plymouth/script.so
 script_lib_plymouth_on_boot_progress () from /usr/lib/x86_64-linux-gnu/plymouth/script.so
 ?? () from /lib/x86_64-linux-gnu/libply-splash-core.so.4
TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
UpgradeStatus: Upgraded to xenial on 2016-07-26 (150 days ago)
UserGroups:

dmi.bios.date: 08/11/2016
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68ICE Ver. F.65
dmi.board.name: 179C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 42.38
dmi.chassis.asset.tag: 6470b
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICEVer.F.65:bd08/11/2016:svnHewlett-Packard:pnHPProBook6470b:pvrA1029C1102:rvnHewlett-Packard:rn179C:rvrKBCVersion42.38:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 6470b
dmi.product.version: A1029C1102
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Fenyvesi Attila (fattila2) 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 #1552370, 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
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plymouth (Ubuntu):
status: New → Confirmed
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.