plymouthd crashed with SIGSEGV in script_lib_plymouth_on_keyboard_input()

Bug #1765159 reported by Prasanna Loganathar
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

Random crash on boot

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: plymouth 0.9.3-1ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
Date: Wed Apr 18 23:53:10 2018
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-02-11 (66 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f2:b50c Chicony Electronics Co., Ltd
 Bus 001 Device 003: ID 8087:07dc Intel Corp.
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP ENVY Notebook
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=82b306a4-50fd-458b-affc-8467a3eb3a1b ro quiet splash acpi_osi=Linux vt.handoff=1
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcEnviron:
 LANG=en_US.utf8
 LANGUAGE=en_US:en
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=82b306a4-50fd-458b-affc-8467a3eb3a1b ro quiet splash acpi_osi=Linux vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x7f71f7a7bb42 <script_lib_plymouth_on_keyboard_input+18>: mov 0x20(%r12),%rsi
 PC (0x7f71f7a7bb42) 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_lib_plymouth_on_keyboard_input () at /usr/lib/x86_64-linux-gnu/plymouth/script.so
 () at /usr/lib/x86_64-linux-gnu/plymouth/script.so
 () at /lib/x86_64-linux-gnu/libply-splash-core.so.4
 ply_event_loop_process_pending_events () at /lib/x86_64-linux-gnu/libply.so.4
 ply_event_loop_run () at /lib/x86_64-linux-gnu/libply.so.4
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in script_lib_plymouth_on_keyboard_input()
UpgradeStatus: Upgraded to bionic on 2018-04-17 (1 days ago)
UserGroups:

dmi.bios.date: 04/07/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.44
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80DD
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 64.38
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.44:bd04/07/2017:svnHewlett-Packard:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80DD:rvr64.38:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
dmi.product.name: HP ENVY Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Prasanna Loganathar (pvl) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.