plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Bug #1763505 reported by Piotr Wieczorek
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

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: Thu Apr 12 22:22:48 2018
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2015-08-18 (968 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 4242A14
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=a84f3b2b-fd49-4dea-8c9c-97e3a8623fec 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=a84f3b2b-fd49-4dea-8c9c-97e3a8623fec ro quiet splash vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x7f5ffd20a480 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7f5ffd20a480) 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 () at /usr/lib/x86_64-linux-gnu/plymouth/script.so
 script_obj_as_custom () at /usr/lib/x86_64-linux-gnu/plymouth/script.so
 script_execute_object () at /usr/lib/x86_64-linux-gnu/plymouth/script.so
 script_lib_plymouth_on_display_normal () at /usr/lib/x86_64-linux-gnu/plymouth/script.so
 () at /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-04-09 (3 days ago)
UserGroups:

dmi.bios.date: 05/14/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: 8AET65WW (1.45 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4242A14
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: 4242A14R9GR4PF
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8AET65WW(1.45):bd05/14/2015:svnLENOVO:pn4242A14:pvrThinkPadT520:rvnLENOVO:rn4242A14:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T520
dmi.product.name: 4242A14
dmi.product.version: ThinkPad T520
dmi.sys.vendor: LENOVO

Revision history for this message
Piotr Wieczorek (pwiecz-f) 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.