Ubuntu
apt-xapian-index package

update-apt-xapian-index crashed with error in meth(): [Errno 2] No such file or directory

Bug #850619 reported by Tim Kornhammar on 2011-09-15

This bug report is a duplicate of: Bug #829387: update-apt-xapian-index crashed with error in meth(): [Errno 2] No such file or directory. Edit Remove

This bug affects 1 person

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

Bug Description

Just booted up my upgraded ubuntu 11.10 beta on my x64 system.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: apt-xapian-index 0.44ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
Date: Sat Sep 10 14:39:04 2011
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --update -q
ProcEnviron:
SHELL=/bin/bash
LANG=sv_SE.UTF-8
PATH=(custom, no user)
PythonArgs: ['/usr/sbin/update-apt-xapian-index', '--update', '-q']
SourcePackage: apt-xapian-index
Title: update-apt-xapian-index crashed with error in meth(): [Errno 2] No such file or directory
UpgradeStatus: Upgraded to oneiric on 2011-09-06 (8 days ago)
UserGroups:

Tags:

Revision history for this message

Tim Kornhammar (tim-kornhammar) wrote on 2011-09-15:

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

Revision history for this message

Apport retracing service (apport) wrote on 2011-09-15: 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 #829387, 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.