plymouthd crashed with SIGSEGV in script_obj_deref_direct()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Bug on startup
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: plymouth 0.9.3-1ubuntu6
ProcVersionSign
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
Date: Sat Apr 7 16:55:58 2018
DefaultPlymouth: /usr/share/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-01-18 (79 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Apple Inc. MacBookPro9,2
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7efd387b3480 <script_
PC (0x7efd387b3480) 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_
script_
script_
script_
?? () from /usr/lib/
TextPlymouth: /usr/share/
Title: plymouthd crashed with SIGSEGV in script_
UpgradeStatus: Upgraded to bionic on 2018-04-06 (1 days ago)
UserGroups:
dmi.bios.date: 08/08/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP91.88Z.
dmi.board.
dmi.board.name: Mac-6F01561E16C
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAppleInc
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro9,2
dmi.product.
dmi.sys.vendor: Apple Inc.
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.