plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

Bug Description

Internal system error, no idea

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: plymouth 0.9.3-1ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
Date: Thu Mar 29 12:10:14 2018
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-03-29 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
MachineType: LENOVO 20AH000GCD
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=22ad885e-6be2-4b93-9076-b22a703af149 ro quiet splash vt.handoff=1
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=22ad885e-6be2-4b93-9076-b22a703af149 ro quiet splash vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x7f32220f2480 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7f32220f2480) ok
 source "$0x1" ok
 destination "(%rdi)" (0x000015a2) 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_display_normal () from /usr/lib/x86_64-linux-gnu/plymouth/script.so
 ?? () 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: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 02/18/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: GGET15WW (1.03 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AH000GCD
dmi.board.vendor: LENOVO
dmi.board.version: Win8 STD PRC DPK TPG
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGGET15WW(1.03):bd02/18/2013:svnLENOVO:pn20AH000GCD:pvrThinkPadX230s:rvnLENOVO:rn20AH000GCD:rvrWin8STDPRCDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230s
dmi.product.name: 20AH000GCD
dmi.product.version: ThinkPad X230s
dmi.sys.vendor: LENOVO

Revision history for this message
Joseph Jeffers (monprin) 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 #1745406, 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.