plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Bug #1750557 reported by Marcos Nascimento
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

This message occurred after I rebooted the PC.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: plymouth 0.9.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Tue Feb 20 09:01:31 2018
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2017-11-12 (100 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171109)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=7b324028-8bf6-4c1e-9c69-76f09230e75b 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.13.0-32-generic.efi.signed root=UUID=7b324028-8bf6-4c1e-9c69-76f09230e75b ro quiet splash vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x7ff96ef8f480 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7ff96ef8f480) ok
 source "$0x1" ok
 destination "(%rdi)" (0x317875615f) 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: 02/25/2011
dmi.bios.vendor: Intel Corp.
dmi.bios.version: IDG4510H.86A.0135.2011.0225.1100
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DG45ID
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE27729-310
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrIDG4510H.86A.0135.2011.0225.1100:bd02/25/2011:svn:pn:pvr:rvnIntelCorporation:rnDG45ID:rvrAAE27729-310:cvn:ct3:cvr:

Revision history for this message
Marcos Nascimento (wstlmn) 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.