plymouthd crashed with SIGSEGV in script_obj_deref_direct()

[Jonas Hendrikson]

No idea what so ever what happened. A few seconds after login I was presented with the automatic crash and bugreport tool. First boot with propriatary NVIDIA drivers.

Installation is somewhat of a franken-buntu. Started its life as xubuntu 17.10. Then replaced with the ubuntu-mate-desktop meta-package. Later ubuntu-desktop. Now on the 18.04 beta. Sorry for this probably useless report. Should I avoid sending reports like this?

jonas@pantzer:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)"

jonas@pantzer:~$ uname -a
Linux pantzer 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

plymouth:
  Installerad: 0.9.3-1ubuntu6
  Kandidat: 0.9.3-1ubuntu6
  Versionstabell:
 *** 0.9.3-1ubuntu6 500
        500 http://se.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: plymouth 0.9.3-1ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
Date: Fri Apr 13 19:49:42 2018
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-01-13 (90 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
Lsusb:
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 252226G
ProcCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcEnviron:
 LANG=sv_SE.UTF-8
 PATH=(custom, no user)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x7f6e3b49b480 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7f6e3b49b480) ok
 source "$0x1" ok
 destination "(%rdi)" (0x00000020) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 script_obj_deref_direct () at /usr/lib/x86_64-linux-gnu/plymouth/script.so
 script_obj_as_custom () at /usr/lib/x86_64-linux-gnu/plymouth/script.so
 script_execute_object () at /usr/lib/x86_64-linux-gnu/plymouth/script.so
 script_lib_plymouth_on_boot_progress () at /usr/lib/x86_64-linux-gnu/plymouth/script.so
 () at /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 script_obj_deref_direct()
UpgradeStatus: Upgraded to bionic on 2018-03-31 (14 days ago)
UserGroups:

dmi.bios.date: 02/14/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 6IET85WW (1.45 )
dmi.board.name: 252226G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn252226G:pvrThinkPadT410:rvnLENOVO:rn252226G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T410
dmi.product.name: 252226G
dmi.product.version: ThinkPad T410
dmi.sys.vendor: LENOVO

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1580078, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.