software-center crashed with SIGSEGV in __cxa_allocate_exception()

Bug #732946 reported by eduardo30
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
software-center (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: software-center

I tried to open the Software Center from the Control Center and it crashed. I don't think it's one time only because I've repeated the bug a couple times now. It's running live if that helps in any way.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: software-center 3.1.23.1
ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
Uname: Linux 2.6.38-6-generic x86_64
Architecture: amd64
Date: Thu Mar 10 23:36:39 2011
ExecutablePath: /usr/share/software-center/software-center
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110310)
PackageArchitecture: all
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: 0x7f9aae284244 <__cxa_allocate_exception+36>: addl $0x1,0x8(%rax)
 PC (0x7f9aae284244) ok
 source "$0x1" ok
 destination "0x8(%rax)" (0x00000018) 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/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

Revision history for this message
eduardo30 (eduardocarrillo30) wrote :
Changed in software-center (Ubuntu):
status: New → Confirmed
Revision history for this message
Gary Lasker (gary-lasker) wrote :

Hi eduardo30, thank you for your report. We've determined that the root cause of this bug is in another package, and that this crasher is in fact a duplicate of bug 259219. We're now tracking the fix for this over at bug 259219, so I will mark this one as a dupe of that.

Note also that a temporary workaround for the software-center crash has been added to the description for bug 259219.

Thanks again!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.