Ubuntu
apt-xapian-index package

update-apt-xapian-index crashed with OverflowError in index()

Bug #656467 reported by Prosthetic Head on 2010-10-07

This bug report is a duplicate of: Bug #635893: update-apt-xapian-index crashed with OverflowError in index(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	apt-xapian-index (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: apt-xapian-index

usng freshly installed and updated 10.01rc 64bit. Apport reported this shortly after logging in.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: apt-xapian-index 0.39ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Thu Oct 7 19:22:57 2010
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate amd64 (20100928)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index -q
ProcEnviron:
PATH=(custom, no user)
SHELL=/bin/sh
PythonArgs: ['/usr/sbin/update-apt-xapian-index', '-q']
SourcePackage: apt-xapian-index
Title: update-apt-xapian-index crashed with OverflowError in index()
UserGroups:

Tags:

Revision history for this message

Prosthetic Head (propanone) wrote on 2010-10-07:

Dependencies.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (33.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (749 bytes, text/plain; charset="utf-8")
Traceback.txt Edit (836 bytes, text/plain; charset="utf-8")

Apport retracing service (apport) on 2010-10-15

tags:

removed: need-duplicate-check

Steve Beattie (sbeattie) on 2011-07-14

visibility:

private → public

Revision history for this message

Robert Roth (evfool) wrote on 2011-09-21:

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 #635893, so it 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. Feel free to continue to report any other bugs you may find.