plymouthd crashed with SIGSEGV in script_obj_deref_direct()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Machine reported there's a problem ... so there you have it.
Machine seems to run fine in spite of it.
Cheers-
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: plymouth 0.9.3-1ubuntu2
ProcVersionSign
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
BootLog: Error: [Errno 2] No such file or directory: '/var/log/boot.log'
Date: Tue Mar 27 06:05:35 2018
DefaultPlymouth: /usr/share/
ExecutablePath: /sbin/plymouthd
MachineType: LENOVO 41732BU
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f347f6bd480 <script_
PC (0x7f347f6bd480) ok
source "$0x1" ok
destination "(%rdi)" (0x2d412d494d44
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
script_
script_
script_
script_
?? () from /usr/lib/
TextPlymouth: /usr/share/
Title: plymouthd crashed with SIGSEGV in script_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 10/12/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: 8CET63WW (1.43 )
dmi.board.
dmi.board.name: 41732BU
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: ThinkPad T420s
dmi.product.name: 41732BU
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 #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.