Ubuntu
apt-xapian-index package

update-apt-xapian-index crashed with DatabaseLockError in init(): Unable to get write lock on /var/cache/apt-xapian-index/index.2: already locked

Bug #775544 reported by Anbu Kaveeswarar Selvaraju on 2011-05-02

This bug report is a duplicate of: Bug #764701: update-apt-xapian-index crashed with DatabaseLockError in __init__(): Unable to get write lock on /var/cache/apt-xapian-index/index.2: already locked. Edit Remove

This bug affects 2 people

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

Bug Description

Binary package hint: apt-xapian-index

using live cd

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: Mon May 2 14:51:15 2011
ExecutablePath: /usr/sbin/update-apt-xapian-index
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --batch-mode --force
ProcEnviron:

PythonArgs: ['/usr/sbin/update-apt-xapian-index', '--batch-mode', '--force']
SourcePackage: apt-xapian-index
Title: update-apt-xapian-index crashed with DatabaseLockError in __init__(): Unable to get write lock on /var/cache/apt-xapian-index/index.2: already locked
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Tags:

Revision history for this message

Anbu Kaveeswarar Selvaraju (anbu-kaveeswarar-selvaraju) wrote on 2011-05-02:

Traceback.txt Edit (663 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 #764701, 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.