plymouthd crashed with SIGSEGV in ply_keyboard_stop_watching_for_renderer_input()

Bug #1816559 reported by Guybrush88
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I got this crash report after I rebooted my PC, but I'm sorry that I don't know how to reproduce it.

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: plymouth 0.9.3-1ubuntu10
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
Date: Tue Feb 19 10:57:23 2019
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
Disassembly: => 0x21: Cannot access memory at address 0x21
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-06-18 (245 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: ASUSTeK COMPUTER INC. K30AD_M31AD_M51AD
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=a9094983-e022-4542-9e83-2c6f4fe4d612 ro quiet splash vt.handoff=1
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcEnviron:
 LANG=it_IT.UTF-8
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=a9094983-e022-4542-9e83-2c6f4fe4d612 ro quiet splash vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x21: Cannot access memory at address 0x21
 PC (0x00000021) 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-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_keyboard_stop_watching_for_input()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 11/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0402
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: K30AD_M31AD_M51AD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0402:bd11/29/2013:svnASUSTeKCOMPUTERINC.:pnK30AD_M31AD_M51AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnK30AD_M31AD_M51AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: Desktop
dmi.product.name: K30AD_M31AD_M51AD
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK COMPUTER INC.
mtime.conffile..etc.apport.crashdb.conf: 2018-10-22T09:50:20.732763

Revision history for this message
Guybrush88 (guybrush) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ply_keyboard_stop_watching_for_renderer_input (keyboard=0x55a798eeebf0) at ply-keyboard.c:406
 ply_keyboard_stop_watching_for_input (keyboard=keyboard@entry=0x55a798eeebf0) at ply-keyboard.c:406
 ply_device_manager_deactivate_keyboards (manager=0x55a798edca60) at ply-device-manager.c:1002
 on_deactivate (state=0x7ffda0317120, deactivate_trigger=<optimized out>) at main.c:1364

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
summary: - plymouthd crashed with SIGSEGV in ply_keyboard_stop_watching_for_input()
+ plymouthd crashed with SIGSEGV in
+ ply_keyboard_stop_watching_for_renderer_input()
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
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.