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 #765198 reported by danieljucan
14
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

Error medium

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 x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Tue Apr 19 00:10:04 2011
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --force --quiet
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF8
PythonArgs: ['/usr/sbin/update-apt-xapian-index', '--force', '--quiet']
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:

Revision history for this message
danieljucan (danieljucan-gmail) wrote :
Revision history for this message
Apport retracing service (apport) wrote : 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.

tags: removed: need-duplicate-check
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apt-xapian-index (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.