plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

Bug Description

ubuntu 18.04 distupgrade from 16.04 @ dell xps 12

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: plymouth 0.9.3-1ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Fri Apr 6 22:46:10 2018
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-03-11 (26 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: Dell Inc. XPS 12 9Q23
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=e8186b16-2ca7-47a4-a261-792524adbc6b ro quiet splash i8042.direct i8042.dumbkbd vt.handoff=1
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=e8186b16-2ca7-47a4-a261-792524adbc6b ro quiet splash i8042.direct i8042.dumbkbd vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x7f2d586be480 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7f2d586be480) ok
 source "$0x1" ok
 destination "(%rdi)" (0xffffffff) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown 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/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
UpgradeStatus: Upgraded to bionic on 2018-03-11 (26 days ago)
UserGroups:

dmi.bios.date: 12/07/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.asset.tag: 0004061282
dmi.board.name: 0520M8
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: 0004061282
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A05
dmi.modalias: dmi:bvnDellInc.:bvrA05:bd12/07/2012:svnDellInc.:pnXPS129Q23:pvrA05:rvnDellInc.:rn0520M8:rvrA00:cvnDellInc.:ct8:cvrA05:
dmi.product.family: 103C_5335KV
dmi.product.name: XPS 12 9Q23
dmi.product.version: A05
dmi.sys.vendor: Dell Inc.

Revision history for this message
Jane Doe (vzezin) 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 #1580078, 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.