plymouthd crashed with SIGSEGV in script_obj_deref_direct() after logon
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This happens right after logging in
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: plymouth 0.9.2-3ubuntu17
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Wed Oct 18 10:49:38 2017
DefaultPlymouth: /usr/share/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2017-10-17 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015)
MachineType: HP HP ZBook Studio G4
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=
ProcFB:
0 EFI VGA
1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f4ab816e420 <script_
PC (0x7f4ab816e420) 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_
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/09/2017
dmi.bios.vendor: HP
dmi.bios.version: P71 Ver. 01.03
dmi.board.name: 826B
dmi.board.vendor: HP
dmi.board.version: KBC Version 47.39
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnHP:
dmi.product.family: 103C_5336AN
dmi.product.name: HP ZBook Studio G4
dmi.sys.vendor: HP
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.