plymouthd crashed with SIGSEGV in ply_buffer_get_size()

[ayem]

Binary package hint: plymouth

my desktop be blank when start.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.2-2
ProcVersionSignature: Ubuntu 2.6.31-18.55-generic
Uname: Linux 2.6.31-18-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CurrentDmesg:
 [ 308.456030] eth0: no IPv6 routers present
 [ 327.324645] ip_tables: (C) 2000-2006 Netfilter Core Team
Date: Sat Apr 17 21:02:27 2010
DefaultPlymouth: /lib/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 15d9:0a33 Dexon Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-18-generic root=UUID=89f42c32-f26a-4aa3-b311-f2b0423c7d6d ro quiet splash
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB:

SegvAnalysis:
 Segfault happened at: 0x379107 <ply_buffer_get_size+7>: mov 0x4(%eax),%eax
 PC (0x00379107) ok
 source "0x4(%eax)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ply_buffer_get_size () from /lib/libply.so.2
 ply_boot_splash_show () from /lib/libply-splash-core.so.2
 ?? ()
 ?? ()
 ?? ()
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_buffer_get_size()
UserGroups:

dmi.bios.date: 05/05/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd05/05/2006:svn:pn:pvr:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #555247, 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.