software-center crashed with SIGSEGV in __cxa_allocate_exception()

[Mathok]

Binary package hint: software-center

software-center crashed after start over graphical interface with the clasic desktop

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: software-center 3.1.23.1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
Architecture: i386
CrashCounter: 1
Date: Wed Mar 9 10:44:41 2011
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
 LANGUAGE=de_DE:en
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x466a6bd <__cxa_allocate_exception+61>: addl $0x1,0x4(%eax)
 PC (0x0466a6bd) 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 libvirtd lpadmin plugdev sambashare

[Gary Lasker (gary-lasker)]

Hello Mathok, thanks very much for taking the time to report this issue. The root cause of this crash has been determined to be in another package, and we are tracking the problem at bug 259219. Therefore, I'll set this bug as a duplicate of that one.

Please also note that a workaround for this crash is software-center has been added in the description for bug 259219.

If you have any comments or further information that you'd like to add, please do so at bug 259219, and please keep an eye on that bug for the status of the fix for this issue.

Thanks again!