soffice.bin crashed with SIGSEGV in uno_type_sequence_construct()

[ledom]

Binary package hint: libreoffice

Closing libreoffice Calc window

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libreoffice-core 1:3.3.2-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
CrashCounter: 1
Date: Wed May 18 17:01:24 2011
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin -calc /media/DATA/Documents/projetsweb/Panierdici/producteurs/Un_point_de_vente_à_la_ferme\ (copie)_3.xls -splash-pipe=5
ProcEnviron:
 LANGUAGE=fr_FR:en
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x24bea1: mov 0x8(%edx),%eax
 PC (0x0024bea1) ok
 source "0x8(%edx)" (0x000002f8) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 ?? () from /usr/lib/libreoffice/program/../basis-link/program/../ure-link/lib/libuno_cppu.so.3
 uno_type_sequence_construct () from /usr/lib/libreoffice/program/../basis-link/program/../ure-link/lib/libuno_cppu.so.3
 ?? () from /usr/lib/libreoffice/program/../basis-link/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3
 cppu::OInterfaceContainerHelper::removeInterface(com::sun::star::uno::Reference<com::sun::star::uno::XInterface> const&) () from /usr/lib/libreoffice/program/../basis-link/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3
 ?? () from /usr/lib/libreoffice/program/../basis-link/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3
Title: soffice.bin crashed with SIGSEGV in uno_type_sequence_construct()
UpgradeStatus: Upgraded to natty on 2011-04-29 (19 days ago)
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev sambashare video www-data

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