plymouthd crashed with SIGSEGV in ply_buffer_get_size()

[Aaron]

Binary package hint: plymouth

This happens every time I boot up the computer, running the latest packages.

Let me know if you need any specific additional information.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.1-4ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
Uname: Linux 2.6.32-16-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sun Apr 11 00:19:46 2010
DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-7235
ProcCmdLine: root=UUID=c4dc8906-b84f-4550-8f54-4abc28d8eb70 ro single
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 VGA16 VGA
SegvAnalysis:
 Segfault happened at: 0x8aa107 <ply_buffer_get_size+7>: mov 0x4(%eax),%eax
 PC (0x008aa107) 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: 06/13/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: MS-7235
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: REV:1.1
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/13/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7235:pvrREV1.1:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7235:rvrREV1.1:cvn:ct3:cvr:
dmi.product.name: MS-7235
dmi.product.version: REV:1.1
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

[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.