plymouthd crashed with SIGSEGV in ply_renderer_get_buffer_for_head()

[Henri Pesch]

Intel nuc5i5ryh; 2*8GB G.Skill F3-2133C11Q-32GRSL ; SSDSC2BW240A401 280GB; SSDSCKGW180A401 180GB M.2.
UBUNTU 15.04 64bit Desktop installed on March 28th, 2015. Ubuntu Vivid Vervet (development branch)).
First occurence of the error at statup in Desktop screen after booting.

Kind Regards, Henri Pesch

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: plymouth 0.9.0-0ubuntu9
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.16.2-0ubuntu5
Architecture: amd64
Date: Sun Mar 29 12:47:39 2015
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2015-03-29 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed root=UUID=a2ae309b-9d54-4928-a4d4-52280a225e1e ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f61d8568b89 <ply_renderer_get_buffer_for_head+9>: mov 0x10(%rdi),%rax
 PC (0x7f61d8568b89) ok
 source "0x10(%rdi)" (0x00000041) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ply_renderer_get_buffer_for_head () from /lib/x86_64-linux-gnu/libply-splash-core.so.4
 ply_pixel_display_draw_area () from /lib/x86_64-linux-gnu/libply-splash-core.so.4
 script_lib_sprite_refresh () from /lib/x86_64-linux-gnu/plymouth/script.so
 ?? () from /lib/x86_64-linux-gnu/plymouth/script.so
 ?? () from /lib/x86_64-linux-gnu/plymouth/script.so
Title: plymouthd crashed with SIGSEGV in ply_renderer_get_buffer_for_head()
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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