plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

Bug Description

Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
plymouth:
  Installed: 0.9.3-1ubuntu6
  Candidate: 0.9.3-1ubuntu6
  Version table:
 *** 0.9.3-1ubuntu6 500
        500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status

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-0ubuntu2
Architecture: amd64
Date: Fri Apr 6 10:31:10 2018
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-04-04 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp.
 Bus 001 Device 002: ID 0bda:5686 Realtek Semiconductor Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude E5470
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=88fe9616-3b97-4625-84fb-f65f68ff77e8 ro quiet splash 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=88fe9616-3b97-4625-84fb-f65f68ff77e8 ro quiet splash vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x7fdcc5c5b480 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7fdcc5c5b480) ok
 source "$0x1" ok
 destination "(%rdi)" (0x2d50442d30647261) 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_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: 06/15/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.3
dmi.board.asset.tag: 3211798
dmi.board.name: 0P88J9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: 3211798
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0P88J9:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5470
dmi.sys.vendor: Dell Inc.

Revision history for this message
Jan (jankronenb) 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.