software-center crashed with SIGSEGV in __cxa_allocate_exception()

[Leo]

Binary package hint: software-center

I can't open Software center

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
Architecture: i386
CrashCounter: 1
Date: Mon Mar 14 09:46:08 2011
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
 LANGUAGE=es_ES:es:en_GB:en
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x367a6bd <__cxa_allocate_exception+61>: addl $0x1,0x4(%eax)
 PC (0x0367a6bd) 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: Upgraded to natty on 2011-03-14 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Glen Luscombe (glenluscombe)]

Hi Leo,

Thanks for taking the time to report this bug and help make Ubuntu better.

You mention that you cannot open the software center - Is this crash repeatable? The stacktrace provided by apport here does not have enough information to progress this bug. If it is at all possible, can you run a backtrace during the crash? Please follow the instructions at https://wiki.ubuntu.com/Backtrace, and post the log file here. The bash command to start the software center is 'software-center'.

[Omer Akram (om26er)]

Thanks for the bug report. This particular bug has already been reported and is a duplicate of bug 259219, so is being marked as such. Any further discussion regarding the bug should occur in the other report. Feel free to report any other bugs you may find