software-center crashed with SIGSEGV in __cxa_allocate_exception()

[Angel Guzman Maeso]

Binary package hint: software-center

This bug appears after https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/733693

Currently I am using fbdev driver on Nvidia GT 8500 (because enabling closed source drivers breaks xorg.conf and if you switch again to open source drivers the xorg it is not generated (only failsafe mode))

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: software-center 3.1.23.1
ProcVersionSignature: Ubuntu 2.6.38-6.34-generic-pae 2.6.38-rc7
Uname: Linux 2.6.38-6-generic-pae i686
Architecture: i386
Date: Sat Mar 12 07:01:18 2011
ExecutablePath: /usr/share/software-center/software-center
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 LANGUAGE=es_ES:en
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb5fc76bd <__cxa_allocate_exception+61>: addl $0x1,0x4(%eax)
 PC (0xb5fc76bd) 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-12 (0 days ago)
UserGroups:

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