plymouthd crashed with SIGSEGV in script_obj_deref_direct()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
i don't know
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: plymouth 0.9.3-1ubuntu1
ProcVersionSign
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Sun Feb 25 15:09:00 2018
DefaultPlymouth: /usr/share/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-01-04 (51 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: LENOVO 80XL
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=
ProcEnviron:
LANG=en_IN
LANGUAGE=en_IN:en
PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f862dbbc494 <script_
PC (0x7f862dbbc494) ok
source "$0x1" ok
destination "(%rax)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
script_
script_
script_
script_
?? ()
TextPlymouth: /usr/share/
Title: plymouthd crashed with SIGSEGV in script_
UpgradeStatus: Upgraded to bionic on 2018-01-05 (50 days ago)
UserGroups:
dmi.bios.date: 09/30/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: 4WCN29WW
dmi.board.
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: ideapad 320-15IKB
dmi.product.name: 80XL
dmi.product.
dmi.sys.vendor: LENOVO
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 #927636, 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.