plymouthd crashed with SIGSEGV in ply_input_device_get_keymap()

Bug #2050743 reported by Adam K
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Plymouth
Fix Released
Unknown
plymouth (Ubuntu)
Fix Released
Medium
Daniel van Vugt

Bug Description

Unsure

ProblemType: Crash
DistroRelease: Ubuntu 24.04
Package: plymouth 23.360.11-0ubuntu2
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Mon Jan 22 18:15:26 2024
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
ExecutablePath: /usr/sbin/plymouthd
InstallationDate: Installed on 2024-01-22 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240122)
JournalErrors: -- No entries --
Lspci:

Lspci-vt:

Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:

Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic root=UUID=be8601a9-912c-475f-a790-c973864eb61f ro quiet splash vt.handoff=7
ProcCmdline: /usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic root=UUID=be8601a9-912c-475f-a790-c973864eb61f ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x766b66f5aeab <ply_input_device_get_keymap+27>: mov 0x40(%rdi),%rdi
 PC (0x766b66f5aeab) ok
 source "0x40(%rdi)" (0x00000040) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ply_input_device_get_keymap () from /lib/x86_64-linux-gnu/libply-splash-core.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/plymouth/renderers/frame-buffer.so
 ply_keymap_icon_new () from /lib/x86_64-linux-gnu/libply-splash-graphics.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/plymouth/two-step.so
 ?? () from /lib/x86_64-linux-gnu/libply-splash-core.so.5
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_input_device_get_keymap()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
dmi.bios.date: 04/06/2022
dmi.bios.release: 4.1
dmi.bios.vendor: Microsoft Corporation
dmi.bios.version: Hyper-V UEFI Release v4.1
dmi.board.asset.tag: None
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: Hyper-V UEFI Release v4.1
dmi.chassis.asset.tag: 4565-7867-8475-0140-6079-1274-47
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: Hyper-V UEFI Release v4.1
dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.1:bd04/06/2022:br4.1:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.1:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.1:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.1:skuNone:
dmi.product.family: Virtual Machine
dmi.product.name: Virtual Machine
dmi.product.sku: None
dmi.product.version: Hyper-V UEFI Release v4.1
dmi.sys.vendor: Microsoft Corporation
separator:

Revision history for this message
Adam K (localdadmin) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ply_input_device_get_keymap (input_device=0x0) at ../src/libply-splash-core/ply-input-device.c:502
 get_keymap (backend=0x5c8077dc0080) at ../src/plugins/renderers/frame-buffer/plugin.c:867
 ply_keymap_icon_fill_keymap_info (keymap_icon=0x5c8077dc53a0) at ../src/libply-splash-graphics/ply-keymap-icon.c:93
 ply_keymap_icon_new (display=display@entry=0x5c8077dbced0, image_dir=0x5c8077d92020 "/usr/share/plymouth/themes//spinner") at ../src/libply-splash-graphics/ply-keymap-icon.c:135
 view_new (display=0x5c8077dbced0, plugin=0x5c8077ddf710) at ../src/plugins/splash/two-step/plugin.c:249

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in plymouth (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plymouth (Ubuntu):
status: New → Confirmed
information type: Private → Public
tags: added: regression-release
Steve Langasek (vorlon)
tags: removed: regression-release
Changed in plymouth:
status: Unknown → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
tags: added: fixed-upstream
Changed in plymouth (Ubuntu):
assignee: nobody → Daniel van Vugt (vanvugt)
Changed in plymouth (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Daniel van Vugt (vanvugt) wrote (last edit ):

Fix for noble attached.

Also confirmed the crash is fixed for me.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the patch Daniel, I've uploaded it now

Changed in plymouth (Ubuntu):
status: In Progress → Fix Committed
Changed in plymouth:
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package plymouth - 23.360.11-0ubuntu3

---------------
plymouth (23.360.11-0ubuntu3) noble; urgency=medium

  * Add renderers-Do-not-assume-all-keyboards-have-LEDs.patch to avoid
    plymouthd from segfaulting on some systems, resulting in missing
    splash screens. (LP: #2050743)

 -- Daniel van Vugt <email address hidden> Thu, 01 Feb 2024 11:18:08 +0800

Changed in plymouth (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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