plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Bug #1745842 reported by Adolfo Jayme Barrientos
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

Probably crashed due to a forced reboot.

Let the stack trace tell its tale (or not).

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: plymouth 0.9.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
Uname: Linux 4.13.0-30-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
Date: Thu Jan 25 17:14:00 2018
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-01-15 (12 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 005: ID 0930:0227 Toshiba Corp.
 Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
 Bus 001 Device 002: ID 04f2:b446 Chicony Electronics Co., Ltd
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: TOSHIBA Satellite C55-B
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-30-generic.efi.signed root=UUID=b27786f8-e52a-405f-86e2-54fbe6dccc69 ro quiet splash vt.handoff=1
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcEnviron:
 LANG=es_MX.UTF-8
 LANGUAGE=es_MX:es
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-30-generic.efi.signed root=UUID=b27786f8-e52a-405f-86e2-54fbe6dccc69 ro quiet splash vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x7fd0afa0e494 <script_obj_deref_direct+20>: cmpl $0x1,(%rax)
 PC (0x7fd0afa0e494) ok
 source "$0x1" ok
 destination "(%rax)" (0x00000021) 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_update_status () from /usr/lib/x86_64-linux-gnu/plymouth/script.so
 ?? ()
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
UpgradeStatus: Upgraded to bionic on 2018-01-18 (9 days ago)
UserGroups:

dmi.bios.date: 07/23/2015
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 5.00
dmi.board.asset.tag: *
dmi.board.name: ZBWAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: *
dmi.modalias: dmi:bvnTOSHIBA:bvr5.00:bd07/23/2015:svnTOSHIBA:pnSatelliteC55-B:pvrPSCMLM-00MTM1:rvnTOSHIBA:rnZBWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*:
dmi.product.family: *
dmi.product.name: Satellite C55-B
dmi.product.version: PSCMLM-00MTM1
dmi.sys.vendor: TOSHIBA

Revision history for this message
Adolfo Jayme Barrientos (fitojb) 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.