plymouthd crashed with SIGSEGV in script_obj_deref_direct()

[KDontenville]

Seems to be related to failure to boot on vanilla gnome desktop xorg indefinite hang during boot but cant be sure.

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-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 2] No such file or directory: '/var/log/boot.log'
Date: Wed Apr 18 00:59:42 2018
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-logo/ubuntu-gnome-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-04-17 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
MachineType: FUJITSU SIEMENS ESPRIMO E5925
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=71827d04-4f6d-4153-b612-dfe0788c0552 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 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=71827d04-4f6d-4153-b612-dfe0788c0552 ro quiet splash vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x7fb2e32f5480 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7fb2e32f5480) 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_display_normal () from /usr/lib/x86_64-linux-gnu/plymouth/script.so
 ?? () 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: 10/09/2008
dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
dmi.bios.version: 6.00 R1.14.2598.A1
dmi.board.name: D2598-A1
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: S26361-D2598-A1
dmi.chassis.type: 3
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.14.2598.A1:bd10/09/2008:svnFUJITSUSIEMENS:pnESPRIMOE5925:pvr:rvnFUJITSUSIEMENS:rnD2598-A1:rvrS26361-D2598-A1:cvnFUJITSUSIEMENS:ct3:cvr:
dmi.product.name: ESPRIMO E5925
dmi.sys.vendor: FUJITSU SIEMENS

[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 #1745406, 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.