plymouthd crashed with SIGSEGV in ply_keyboard_stop_watching_for_renderer_input()

[Reiner Jung]

The crash report popped up after startup and login. Maybe this is due to an issue during shutdown. However, I did not had any issues during shutdown.

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: plymouth 0.9.3-1ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
Date: Sat Sep 29 20:40:21 2018
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-budgie-logo/ubuntu-budgie-logo.plymouth
Disassembly: => 0x121: Cannot access memory at address 0x121
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-07-20 (72 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: SAMSUNG ELECTRONICS CO., LTD. N150P
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=a2119d63-26c2-4b52-855a-e902c4dcb922 ro quiet splash vt.handoff=1
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=a2119d63-26c2-4b52-855a-e902c4dcb922 ro quiet splash vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x121: Cannot access memory at address 0x121
 PC (0x00000121) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ?? ()
 ply_keyboard_stop_watching_for_input () from /lib/x86_64-linux-gnu/libply-splash-core.so.4
 ply_device_manager_deactivate_keyboards () from /lib/x86_64-linux-gnu/libply-splash-core.so.4
 ?? ()
 ?? ()
TextPlymouth: /usr/share/plymouth/themes/ubuntu-budgie-text/ubuntu-budgie-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_keyboard_stop_watching_for_input()
UpgradeStatus: Upgraded to cosmic on 2018-09-29 (1 days ago)
UserGroups:

dmi.bios.date: 12/20/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 01GT.M026.20101220.RHU
dmi.board.asset.tag: SAMSUNG
dmi.board.name: N150P
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr01GT.M026.20101220.RHU:bd12/20/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnN150P:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN150P:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: N150P
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ply_keyboard_stop_watching_for_renderer_input (keyboard=0x561ce4852380) at ply-keyboard.c:406
 ply_keyboard_stop_watching_for_input (keyboard=keyboard@entry=0x561ce4852380) at ply-keyboard.c:406
 ply_device_manager_deactivate_keyboards (manager=0x561ce4843a60) at ply-device-manager.c:976
 on_quit (state=0x7fffe68b3630, retain_splash=<optimized out>, quit_trigger=0x561ce483f390) at main.c:1435

[Eduardo Barretto (ebarretto)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.