[Bug 1794292] Re: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_input -> ply_device_manager_deactivate_keyboards -> on_deactivate

[Gert van de Kraats]

Problem not solved.

I think I got 4 problems:

1)
I think the second ppa (*mtrudel2*) has exacly same contents as the first one. 
At least the binaries and shared loadlibraries have the same time stamp (15 october).
So this will not contain the last version.

2) 
I have the idea the shared loadlibs are not overwritten at the install.

3)
The file /etc/plymouth/plymouthd.cfg, containing local settings was overwritten. 
I do not know if this is caused by "apt-get install" or by "make install" on localcode.
According to contents of this file, this should not occur.

4)
My proposed fix solves a bug, but probably not the problem.
To verify updating of the loadlibs I did "make install" with my own local code including an extra tracing message.
This crashed again with the usual stacktrace.
I include the plymouth trace plymouth-debug_GK91.log.
After the 5 seconds device timeout (caused by the missing setting to 10 seconds at /etc/plymouth/plymouthd.cfg)
the frame buffer device /dev/fb0 is activated, because drm still not initialized.
Also keyboard is activated for fb0.
Later on the is en event: got remove event for device fb0,
causing "ply_renderer_free:Unloading renderer backend plugin".
At the end the keyboards are deactivated including the one for fb0,
which is pointing to a non-existing backend. 
So I think also the keyboard should be removed (if present) 
if a device is removed.
This should avoid the crash. but I doubt the splash will be displayed correctly.
At my slow PC the problem is always reproducable by setting the timeout to 1.


** Attachment added: "plymouth-debug_GK91.log"
   https://bugs.launchpad.net/ubuntu/cosmic/+source/plymouth/+bug/1794292/+attachment/5209295/+files/plymouth-debug_GK91.log

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1794292

Title:
  plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in
  ply_renderer_set_handler_for_input_source ->
  ply_keyboard_stop_watching_for_renderer_input ->
  ply_keyboard_stop_watching_for_input ->
  ply_device_manager_deactivate_keyboards -> on_deactivate

Status in plymouth package in Ubuntu:
  Confirmed
Status in plymouth source package in Cosmic:
  Confirmed

Bug description:
  A green Xubuntu splash screen with a spinning circle normally appears
  on boot up.

  Now just a blank black screen shows until the login box appears. On
  logging in, the desktop appears as normal but an error message pops up
  offering to report a bug to developers.

  Description:	Ubuntu Cosmic Cuttlefish (development branch)
  Release:	18.10

  All packages up-to-date as of 25 September 2018 14:00 BST

  
  Errors Tracker: https://errors.ubuntu.com/problem/6aa06f1bc51946c787a01d38e58bc76114555334

  
  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
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Sep 25 13:47:47 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ExecutablePath: /sbin/plymouthd
  MachineType: Acer Veriton N280G
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=ff708f10-3fbc-4fa2-b7a5-93f0dd61eb21 ro splash quiet vt.handoff=1
  ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
  ProcEnviron:
   LANG=en_GB.UTF-8
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=ff708f10-3fbc-4fa2-b7a5-93f0dd61eb21 ro splash quiet vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x7f05452a07f9 <ply_renderer_set_handler_for_input_source+25>:	mov    0x78(%rax),%rax
   PC (0x7f05452a07f9) ok
   source "0x78(%rax)" (0x00000078) not located in a known VMA region (needed readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: plymouth
  StacktraceTop:
   ply_renderer_set_handler_for_input_source () from /lib/x86_64-linux-gnu/libply-splash-core.so.4
   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/xubuntu-text/xubuntu-text.plymouth
  Title: plymouthd crashed with SIGSEGV in ply_renderer_set_handler_for_input_source()
  UpgradeStatus: Upgraded to cosmic on 2018-08-21 (34 days ago)
  UserGroups:

  dmi.bios.date: 01/15/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: P01-A3
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TPDS03
  dmi.board.vendor: Acer
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: dmi:bvnAcer:bvrP01-A3:bd01/15/2011:svnAcer:pnVeritonN280G:pvrToBeFilledByO.E.M.:rvnAcer:rnTPDS03:rvrTobefilledbyO.E.M.:cvnAcer:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: Acer Desktop
  dmi.product.name: Veriton N280G
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+subscriptions