plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Bug #1748554 reported by Joonas Tuomola
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-1ubuntu1
  Candidate: 0.9.3-1ubuntu1
  Version table:
 *** 0.9.3-1ubuntu1 500
        500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status

It crashes everytime I boot up Ubuntu.

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-0ubuntu8
Architecture: amd64
CrashCounter: 1
Date: Fri Feb 9 23:57:51 2018
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-02-02 (7 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128)
MachineType: FUJITSU LIFEBOOK E780
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=5f819daa-77fa-4e43-be13-35ac078f5b05 ro quiet splash vt.handoff=1
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcEnviron:
 LANG=fi_FI.UTF-8
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=5f819daa-77fa-4e43-be13-35ac078f5b05 ro quiet splash vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x7fe818867480 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7fe818867480) ok
 source "$0x1" ok
 destination "(%rdi)" (0x00000000) 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_boot_progress () from /usr/lib/x86_64-linux-gnu/plymouth/script.so
 ?? () from /lib/x86_64-linux-gnu/libply-splash-core.so.4
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: 09/06/2010
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.18
dmi.board.name: FJNB210
dmi.board.vendor: FUJITSU
dmi.board.version: CP477720-02
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.chassis.version: E78__
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd09/06/2010:svnFUJITSU:pnLIFEBOOKE780:pvr:rvnFUJITSU:rnFJNB210:rvrCP477720-02:cvnFUJITSU:ct10:cvrE78__:
dmi.product.name: LIFEBOOK E780
dmi.sys.vendor: FUJITSU

Revision history for this message
Joonas Tuomola (pave99) 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 #1580078, 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.