Ubuntu
apt-xapian-index package

update-apt-xapian-index crashed with NameError in slave(): global name 'progress' is not defined

Bug #746680 reported by Alexander Langanke on 2011-03-31

This bug report is a duplicate of: Bug #650869: update-apt-xapian-index crashed with NameError in slave(). 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

After last Update and use of the janitor tool banshee was gone. Trying to reinstall it via software center resulted in the bug.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: apt-xapian-index 0.41ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Mar 31 21:49:16 2011
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --batch-mode --force --update
ProcEnviron:

PythonArgs: ['/usr/sbin/update-apt-xapian-index', '--batch-mode', '--force', '--update']
SourcePackage: apt-xapian-index
Title: update-apt-xapian-index crashed with NameError in slave(): global name 'progress' is not defined
UpgradeStatus: Upgraded to natty on 2011-03-25 (6 days ago)
UserGroups:

Tags:

Revision history for this message

Alexander Langanke (alexlanganke) wrote on 2011-03-31:

Traceback.txt Edit (321 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-03-31: 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 #650869, 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.