software-center crashed with SIGSEGV in __cxa_allocate_exception()

Bug #732799 reported by Don Owen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
software-center (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: software-center

Tried to install the downloaded nautilus-dropbox deb package from Firefox auto-launch.

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
CrashCounter: 1
Date: Thu Mar 10 13:40:53 2011
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110309)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center /tmp/nautilus-dropbox_0.6.7_amd64.deb
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f5421045244 <__cxa_allocate_exception+36>: addl $0x1,0x8(%rax)
 PC (0x7f5421045244) 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 dip fax floppy fuse lpadmin plugdev sambashare tape video

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #732033, 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.

visibility: private → public
tags: removed: need-amd64-retrace
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.