plymouthd crashed with SIGSEGV in script_lib_plymouth_on_keyboard_input()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
display error, init ubuntu then reboot low batery
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: plymouth 0.9.3-1ubuntu4
ProcVersionSign
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
Date: Sun Apr 1 12:14:42 2018
DefaultPlymouth: /usr/share/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2017-04-13 (353 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: LENOVO 2349GV7
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7fbf6baf3b42 <script_
PC (0x7fbf6baf3b42) ok
source "0x20(%r12)" (0x00000041) not located in a known VMA region (needed readable region)!
destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
script_
?? () from /usr/lib/
?? () from /lib/x86_
ply_event_
ply_event_loop_run () from /lib/x86_
TextPlymouth: /usr/share/
Title: plymouthd crashed with SIGSEGV in script_
UpgradeStatus: Upgraded to bionic on 2017-11-26 (126 days ago)
UserGroups:
dmi.bios.date: 05/25/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: G1ET41WW (1.16 )
dmi.board.
dmi.board.name: 2349GV7
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 T430
dmi.product.name: 2349GV7
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 #1757013, 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.