Ubuntu
apt-xapian-index package

update-apt-xapian-index crashed with OSError in finished(): [Errno 2] Aucun fichier ou dossier de ce type

Bug #769017 reported by Bruno Faverdin on 2011-04-22

This bug report is a duplicate of: Bug #751315: update-apt-xapian-index crashed with OSError in finished(): [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

Binary package hint: apt-xapian-index

Crash at startup after reboot

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: apt-xapian-index 0.41ubuntu6
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Fri Apr 22 16:27:42 2011
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --update -q
ProcEnviron:
LANGUAGE=fr_FR:en
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/sbin/update-apt-xapian-index', '--update', '-q']
SourcePackage: apt-xapian-index
Title: update-apt-xapian-index crashed with OSError in finished(): [Errno 2] Aucun fichier ou dossier de ce type
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Tags:

Revision history for this message

Bruno Faverdin (bruno-faverdin) wrote on 2011-04-22:

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

Revision history for this message

Apport retracing service (apport) wrote on 2011-06-07: 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 #751315, 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.