plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

Bug Description

crash at startup, after just login

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: plymouth 0.9.3-1ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
Date: Tue Apr 17 14:23:27 2018
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-logo/ubuntu-gnome-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-04-16 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
MachineType: FUJITSU LIFEBOOK U757
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed root=UUID=8f71b12f-121c-4407-8496-594f40da88be ro quiet splash vt.handoff=1
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed root=UUID=8f71b12f-121c-4407-8496-594f40da88be ro quiet splash vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x7f0469855480 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7f0469855480) ok
 source "$0x1" ok
 destination "(%rdi)" (0x2d412d494d44482d) 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-gnome-text/ubuntu-gnome-text.plymouth
Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 11/07/2017
dmi.bios.vendor: FUJITSU // Insyde Software Corp.
dmi.bios.version: Version 1.18
dmi.board.name: FJNB2A5
dmi.board.vendor: FUJITSU
dmi.board.version: K3
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.chassis.version: LIFEBOOK U757
dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.18:bd11/07/2017:svnFUJITSU:pnLIFEBOOKU757:pvr10601736746:rvnFUJITSU:rnFJNB2A5:rvrK3:cvnFUJITSU:ct10:cvrLIFEBOOKU757:
dmi.product.family: LIFEBOOK-FTS
dmi.product.name: LIFEBOOK U757
dmi.product.version: 10601736746
dmi.sys.vendor: FUJITSU

Revision history for this message
Xavier Farret (xfarret) 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.