software-center crashed with SIGSEGV in __cxa_allocate_exception()

Bug #746778 reported by Giuseppe Buzzanca (PiDy)
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
software-center (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: software-center

I search for chromium browser in the unity search box, then the installation process starts, but the software center crash

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 x86_64
Architecture: amd64
Date: Thu Mar 31 23:48:30 2011
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center chromium-browser/Browser\ web\ Chromium
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=it_IT:en
 LANG=it_IT.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f3a9fb57244 <__cxa_allocate_exception+36>: addl $0x1,0x8(%rax)
 PC (0x7f3a9fb57244) 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
Giuseppe Buzzanca (PiDy) (giuseppebuzzanca) wrote :
visibility: private → public
Revision history for this message
Gary Lasker (gary-lasker) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 259219, so it is being marked as such. If you look at bug 259219, you'll see that the fix for this bug has been released, and you can get the fix by updating your system to the latest Natty packages. Do do this, please use update-manager or type the following at the command line:

  sudo apt-get update
  sudo apt-get dist-upgrade

Please let us know if you still encounter this problem after a full update. And thanks again!

Changed in software-center (Ubuntu):
status: New → Confirmed
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.