plymouthd crashed with SIGSEGV in script_obj_deref_direct()

[Cyborg Cygnus]

So I just wanted to clarify this is xubuntu 14.04 daily, xubuntu is my main o/s on the hdd & I deleted 2 other o/s's off of the drive using gparted, I then ran a terminal with the command "sudo update-grub", now when I boot into xubuntu it takes a while to boot & shows this as soon as the desktop loads. http://www.zimagez.com/zimage/screenshot-220314-214814.php

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: plymouth 0.8.8-0ubuntu15
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
Uname: Linux 3.13.0-18-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Mar 22 21:42:56 2014
DefaultPlymouth: /lib/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2014-02-17 (33 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121.1)
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic root=UUID=fa5f4bbc-f04e-4d3f-a0bd-a8fffd337691 ro quiet splash vt.handoff=7
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic root=UUID=fa5f4bbc-f04e-4d3f-a0bd-a8fffd337691 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f635c70e430 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7f635c70e430) ok
 source "$0x1" ok
 destination "(%rdi)" (0x726f207465792079) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 script_obj_deref_direct () from /lib/x86_64-linux-gnu/plymouth/script.so
 script_obj_as_custom () from /lib/x86_64-linux-gnu/plymouth/script.so
 script_execute_object () from /lib/x86_64-linux-gnu/plymouth/script.so
 script_lib_plymouth_on_display_message () from /lib/x86_64-linux-gnu/plymouth/script.so
 ?? () from /lib/x86_64-linux-gnu/plymouth/script.so
TextPlymouth: /lib/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 08/06/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0803
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P6X58D-E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/06/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Apport retracing service (apport)]

StacktraceTop:
 script_obj_deref_direct (obj=0x726f207465792079) at ./script-object.c:132
 script_obj_as_custom (obj=<optimized out>, obj@entry=0x726f207465792079, user_func=user_func@entry=0x7f635c70df60 <script_obj_execute>, user_data=user_data@entry=0x7fff6ccd5f20) at ./script-object.c:237
 script_execute_object_with_parlist (parameter_data=0x77c1e0, this=0x0, obj=0x726f207465792079, state=0x783490) at ./script-execute.c:286
 script_execute_object (state=state@entry=0x783490, function=0x726f207465792079, this=this@entry=0x0, first_arg=first_arg@entry=0x7bc100) at ./script-execute.c:667
 script_lib_plymouth_on_display_message (state=0x783490, data=0x790480, message=message@entry=0x790480 "The disk drive for UUID=c612c271-d752-4882-b2e8-7a707b168cd9 is not ready yet or not present.") at ./script-lib-plymouth.c:308

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Dora (tiggernut24)]

I'm having the same problem with Ubuntu 14.04 running the Gnome shell with whatever that faster feature is, but without the graphic acceleraton. It started when I made some changes in the color of the top bar on my screen.

Dora