plymouthd crashed with SIGSEGV after login

[James Wilson]

Immediately after login after reboot.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: plymouth 0.9.0-0ubuntu9
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic x86_64
ApportVersion: 2.17-0ubuntu2
Architecture: amd64
Date: Fri Apr 10 09:45:37 2015
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2015-03-20 (20 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150320)
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic.efi.signed root=UUID=0312c13e-e481-4cdc-9ef5-140b5cdaa788 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f3b84ab6b89 <ply_renderer_get_buffer_for_head+9>: mov 0x10(%rdi),%rax
 PC (0x7f3b84ab6b89) ok
 source "0x10(%rdi)" (0x00000031) 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.