[Bug 1542000] Re: plymouthd crashed with SIGSEGV in script_obj_deref_direct()

[Janne Snabb]

Happens every time after login on fresh install of Ubuntu GNOME 17.04.
Happened also with few previous releases of Ubuntu.

Reproducible: always on every Ubuntu installation

Not dependent on hardware as it happens on virtual box VMs as well as on
physical machines.

This gives a very bad impression of Ubuntu and Linux in general. New
users are wondering why their freshly installed computers keep producing
scary looking system problems. It makes the whole Ubuntu system feel
unreliable.

Please replace/remove plymouth from Ubuntu!

-- 
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/1542000

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Status in plymouth package in Ubuntu:
  Confirmed

Bug description:
  when start login screen plimuth crash and auto login don't start.
  Start login screen GDM3

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: plymouth 0.9.2-3ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Thu Feb  4 20:19:23 2016
  DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-logo/ubuntu-gnome-logo.plymouth
  ExecutablePath: /sbin/plymouthd
  InstallationDate: Installed on 2016-01-27 (8 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
  MachineType: LENOVO 80EW
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=96e91037-4caa-46d6-b0b0-ecc19860fae0 ro quiet splash vt.handoff=7
  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 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=96e91037-4caa-46d6-b0b0-ecc19860fae0 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7fac854ff660 <script_obj_deref_direct>:	cmpl   $0x1,(%rdi)
   PC (0x7fac854ff660) ok
   source "$0x1" ok
   destination "(%rdi)" (0x00000000) not located in a known VMA region (needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: plymouth
  StacktraceTop:
   script_obj_deref_direct () from /usr/lib/x86_64-linux-gnu/plymouth/script.so
   script_obj_as_custom () from /usr/lib/x86_64-linux-gnu/plymouth/script.so
   script_execute_object () from /usr/lib/x86_64-linux-gnu/plymouth/script.so
   script_lib_plymouth_on_update_status () from /usr/lib/x86_64-linux-gnu/plymouth/script.so
   ?? ()
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth
  Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A8CN47WW(V3.00)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo B50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B50-80
  dmi.modalias: dmi:bvnLENOVO:bvrA8CN47WW(V3.00):bd07/14/2015:svnLENOVO:pn80EW:pvrLenovoB50-80:rvnLENOVO:rnLenovoB50-80:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoB50-80:
  dmi.product.name: 80EW
  dmi.product.version: Lenovo B50-80
  dmi.sys.vendor: LENOVO

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