plymouthd crashed with SIGSEGV in ply_renderer_set_handler_for_input_source()

Bug #1796534 reported by Chris Guiver on 2018-10-07
58
This bug affects 12 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Medium
Unassigned

Bug Description

summary - updated [my x86 system] ~5 mins ago, rebooted & apport-crash again...

Boot up looked normal, this is a test system installed a couple of days ago (QA test; xubuntu 18.10 x86 install
)
It has been booted twice today, it occurred both times. I 'dist-upgrade' during first boot today, then boot to see if it happened again - yep.

I read the https://bugs.launchpad.net/bugs/1794292 which I selected first boot, which may be same issue, but I don't get a black plymouth screen (mine looks normal; my description is different), the crash window after login is the only indicator of anything unusual.

--- update
I rebooted (3rd time) - plymouth screen was black, non-central XUBUNTU in text (about 1/4 from top left) with dots underneath it changing in intensity (maybe I wasn't paying enough attention before; and it better matches description of #1794292. I rebooted again (4th) and plymouth is just like 3rd time...

hardware summary: hp dx6120mt (mini-tower, pentium 4 dual core, 3gb, nvidia 7600gt)

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: plymouth 0.9.3-1ubuntu9
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic i686
ApportVersion: 2.20.10-0ubuntu11
Architecture: i386
BootLog: Error: [Errno 2] No such file or directory: '/var/log/boot.log'
CrashCounter: 1
Date: Sun Oct 7 13:56:35 2018
DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-10-05 (2 days ago)
InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta i386 (20181004)
MachineType: Hewlett-Packard HP Compaq dx6120 MT(PL926AV)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d02d6611-54cb-4373-bdf5-4f3bf6ed760b ro quiet splash vt.handoff=1
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcEnviron:
 LANG=en_AU.UTF-8
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d02d6611-54cb-4373-bdf5-4f3bf6ed760b ro quiet splash vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0xb7f079f9 <ply_renderer_set_handler_for_input_source+41>: mov 0x3c(%edx),%eax
 PC (0xb7f079f9) ok
 source "0x3c(%edx)" (0x3833696b) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ply_renderer_set_handler_for_input_source () from /lib/i386-linux-gnu/libply-splash-core.so.4
 ply_keyboard_stop_watching_for_input () from /lib/i386-linux-gnu/libply-splash-core.so.4
 ply_device_manager_deactivate_keyboards () from /lib/i386-linux-gnu/libply-splash-core.so.4
 ?? ()
 _start ()
TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_renderer_set_handler_for_input_source()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 12/01/2004
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786C2 v01.02
dmi.board.name: 09CCh
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr786C2v01.02:bd12/01/2004:svnHewlett-Packard:pnHPCompaqdx6120MT(PL926AV):pvr:rvnHewlett-Packard:rn09CCh:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP Compaq dx6120 MT(PL926AV)
dmi.sys.vendor: Hewlett-Packard

Chris Guiver (guiverc) wrote :

This crash has the same stack trace characteristics as bug #1794292. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

tags: added: regression-retracer

StacktraceTop:
 ply_renderer_set_handler_for_input_source (renderer=<optimized out>, input_source=0x2472170, handler=0x0, user_data=0x0) at ply-renderer.c:406
 ply_keyboard_stop_watching_for_renderer_input (keyboard=0x2473320) at ply-keyboard.c:406
 ply_keyboard_stop_watching_for_input (keyboard=0x2473320) at ply-keyboard.c:406
 ply_device_manager_deactivate_keyboards (manager=0x2465320) at ply-device-manager.c:976
 on_quit (state=0xbfbad1d8, retain_splash=false, quit_trigger=0x2468920) at main.c:1435

Changed in plymouth (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Chris Guiver (guiverc) on 2018-10-07
information type: Private → Public
Launchpad Janitor (janitor) wrote :

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

Changed in plymouth (Ubuntu):
status: New → Confirmed
Chris Guiver (guiverc) on 2018-10-07
description: updated
Chris Guiver (guiverc) on 2018-10-07
description: updated
Jack Howarth (jwhowarth) wrote :

I was able to suppress these fatal crashes in plymouth that launched the bug reporter on that package under current 18.10 Cosmic by building and installing the 0.9.3-1ubuntu12 release on launchpad

https://launchpad.net/ubuntu/+source/plymouth

from the disco dingo proposed updates. There are no obvious problems with plymouth now.

Sebastien Bacher (seb128) wrote :

@Jack, thanks for the comment, it indeed seems the same segfault as bug #1794292 which is fixed in that update

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

Other bug subscribers