plymouthd crashed with SIGSEGV in ply_renderer_set_handler_for_input_source()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
just started and done apt update+upgrade
corrado@
Linux corrado-
corrado@
System:
Host: corrado-
bits: 64 compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.0
Distro: Ubuntu 18.10 (Cosmic Cuttlefish)
Machine:
Type: Laptop System: Hewlett-Packard product: HP 250 G3 Notebook PC
v: 099110000000000
Mobo: Hewlett-Packard model: 2211 v: 86.49 serial: <root required>
UEFI: Insyde v: F.36 date: 12/18/2014
Battery:
ID-1: BAT1 charge: 13.9 Wh condition: 21.0/21.0 Wh (100%)
model: 13-42 OA03031 status: Charging
CPU:
Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT MCP
arch: Haswell rev: 1 L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19155
Speed: 898 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 895 2: 864
3: 879 4: 858
Graphics:
Device-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel
bus ID: 00:02.0
Display: x11 server: X.Org 1.20.1 driver: i915 resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 18.1.5
direct render: Yes
Audio:
Device-1: Intel Haswell-ULT HD Audio driver: snd_hda_intel v: kernel
bus ID: 00:03.0
Device-2: Intel 8 Series HD Audio driver: snd_hda_intel v: kernel
bus ID: 00:1b.0
Sound Server: ALSA v: k4.19.0-
Network:
Device-1: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169
v: kernel port: 3000 bus ID: 08:00.0
IF: enp8s0 state: down mac: 5c:b9:01:06:ba:ce
Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe driver: rt2800pci
v: 2.3.0 bus ID: 09:00.0
IF: wlp9s0f0 state: up mac: ac:d1:b8:82:03:5d
Drives:
Local Storage: total: 465.76 GiB used: 9.73 GiB (2.1%)
ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 465.76 GiB
Partition:
ID-1: / size: 31.25 GiB used: 9.72 GiB (31.1%) fs: ext4 dev: /dev/sda7
ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors:
System Temperatures: cpu: 45.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 207 Uptime: 5m Memory: 3.78 GiB used: 1.09 GiB (28.7%)
Init: systemd runlevel: 5 Compilers: gcc: N/A Shell: bash v: 4.4.19
inxi: 3.0.22
corrado@
ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: plymouth 0.9.3-1ubuntu8
Uname: Linux 4.19.0-
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
Date: Wed Sep 19 17:02:36 2018
DefaultPlymouth: /usr/share/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-09-12 (7 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180911)
MachineType: Hewlett-Packard HP 250 G3 Notebook PC
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7ffbcc8c17f9 <ply_renderer_
PC (0x7ffbcc8c17f9) ok
source "0x78(%rax)" (0x00000078) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
ply_renderer_
ply_keyboard_
ply_device_
?? ()
?? ()
TextPlymouth: /usr/share/
Title: plymouthd crashed with SIGSEGV in ply_renderer_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 12/18/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.36
dmi.board.
dmi.board.name: 2211
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 86.49
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.
dmi.modalias: dmi:bvnInsyde:
dmi.product.family: 103C_5336AN G=N L=CON B=HP S=PAV
dmi.product.name: HP 250 G3 Notebook PC
dmi.product.sku: J4R70EA#ABZ
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 #1769241, 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.