plymouthd crashed with SIGSEGV in script_obj_deref_direct()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Don't crash the computer, only i receive the report of software failure.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: plymouth 0.9.3-1ubuntu6
ProcVersionSign
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Thu Apr 12 09:18:40 2018
DefaultPlymouth: /usr/share/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-04-08 (4 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180407)
MachineType: Hewlett-Packard HP Pro x2 410 G1 PC
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=
ProcEnviron:
LANG=es_MX.UTF-8
LANGUAGE=es_MX:es
PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7fc35541a494 <script_
PC (0x7fc35541a494) 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: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 06/03/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.25
dmi.board.
dmi.board.name: 21F0
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 53.0D
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.
dmi.modalias: dmi:bvnInsyde:
dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=410 X=Null
dmi.product.name: HP Pro x2 410 G1 PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
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.