software-center crashed with SIGSEGV in __cxa_allocate_exception()

[mfmj_linux]

Binary package hint: software-center

1)Description: Ubuntu Natty (development branch)
Release: 11.04

2) N:Unable to locate package pkgname

3) I want to launch the Ubuntu Software Center.

4) The Ubuntu Software Center did not launch and error occur.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: software-center 3.1.23.2
ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
Uname: Linux 2.6.38-6-generic i686
NonfreeKernelModules: wl
Architecture: i386
CrashCounter: 1
Date: Mon Mar 14 12:41:01 2011
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x15ee6bd <__cxa_allocate_exception+61>: addl $0x1,0x4(%eax)
 PC (0x015ee6bd) ok
 source "$0x1" ok
 destination "0x4(%eax)" (0x0000000c) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: software-center
StacktraceTop:
 __cxa_allocate_exception () from /usr/lib/libstdc++.so.6
 Xapian::Database::Database(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) () from /usr/lib/sse2/libxapian.so.22
 ?? () from /usr/lib/python2.7/dist-packages/xapian/_xapian.so
 PyEval_EvalFrameEx ()
 PyEval_EvalCodeEx ()
Title: software-center crashed with SIGSEGV in __cxa_allocate_exception()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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