plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Bug #1762022 reported by Dominique Meeùs
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

Automatic bug report

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
Date: Sat Apr 7 18:41:03 2018
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-logo/ubuntu-gnome-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-04-07 (0 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Dell Inc. Latitude E5440
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=4fe3a93d-16af-478f-9c19-c54e19359dab ro quiet splash vt.handoff=1
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcEnviron:
 LANG=fr_BE.UTF-8
 LANGUAGE=fr_BE:fr
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=4fe3a93d-16af-478f-9c19-c54e19359dab ro quiet splash vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x7f8171aa7480 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7f8171aa7480) ok
 source "$0x1" ok
 destination "(%rdi)" (0x00000040) 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-gnome-text/ubuntu-gnome-text.plymouth
Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
UpgradeStatus: Upgraded to bionic on 2018-04-07 (0 days ago)
UserGroups:

dmi.bios.date: 01/06/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0WV8K7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA14:bd01/06/2016:svnDellInc.:pnLatitudeE5440:pvr00:rvnDellInc.:rn0WV8K7:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5440
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.

Revision history for this message
Dominique Meeùs (dominiquem) 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.