plymouthd crashed with SIGSEGV in ply_renderer_set_handler_for_input_source()

Bug #1769241 reported by Nathanael Inkson on 2018-05-04
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Medium
Unassigned

Bug Description

crashed on startup

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: plymouth 0.9.3-1ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Mon Apr 30 22:07:47 2018
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-logo/ubuntu-gnome-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2016-11-11 (539 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: ASUS All Series
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=fec6f87a-a3ae-41ce-8d12-fad0411d4749 ro quiet splash vt.handoff=1
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcEnviron:
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=fec6f87a-a3ae-41ce-8d12-fad0411d4749 ro quiet splash vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x7f7235d0bf11 <ply_renderer_set_handler_for_input_source+33>: jmpq *%rax
 PC (0x7f7235d0bf11) ok
 source "*%rax" (0x3f8000003f800000) not located in a known VMA region (needed readable region)!
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ply_renderer_set_handler_for_input_source () at /lib/x86_64-linux-gnu/libply-splash-core.so.4
 ply_keyboard_stop_watching_for_input () at /lib/x86_64-linux-gnu/libply-splash-core.so.4
 ply_device_manager_deactivate_keyboards () at /lib/x86_64-linux-gnu/libply-splash-core.so.4
 ()
 ()
TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_renderer_set_handler_for_input_source()
UpgradeStatus: Upgraded to bionic on 2018-04-16 (17 days ago)
UserGroups:

dmi.bios.date: 05/17/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1007
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1007:bd05/17/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

StacktraceTop:
 ply_renderer_set_handler_for_input_source (renderer=<optimized out>, input_source=0x560fc5d949a0, handler=0x0, user_data=0x0) at ply-renderer.c:406
 ply_keyboard_stop_watching_for_renderer_input (keyboard=0x560fc5d96320) at ply-keyboard.c:319
 ply_keyboard_stop_watching_for_input (keyboard=keyboard@entry=0x560fc5d96320) at ply-keyboard.c:406
 ply_device_manager_deactivate_keyboards (manager=0x560fc5d85a50) at ply-device-manager.c:976
 on_deactivate (state=0x7fff80563270, deactivate_trigger=<optimized out>) at main.c:1353

Changed in plymouth (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
tags: added: cosmic
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
Faustino L. Padilla (arhx) wrote :

I'm having these issue on Ubuntu 18.10 (development branch). I've attached the plymouth log below.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers