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.1: Couldn't fork: Cannot allocate memory

Bug #867834 reported by Vincent Zweije on 2011-10-04

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 3 people

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

Bug Description

Issue surfaced when unlocking screen after manually locking it.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: apt-xapian-index 0.44ubuntu4
Uname: Linux 2.6.38-1000-ac100 armv7l
ApportVersion: 1.23-0ubuntu2
Architecture: armel
Date: Tue Oct 4 21:21:24 2011
ExecutablePath: /usr/sbin/update-apt-xapian-index
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --quiet
ProcEnviron:
PATH=(custom, no user)
SHELL=/bin/sh
PythonArgs: ['/usr/sbin/update-apt-xapian-index', '--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.1: Couldn't fork: Cannot allocate memory
UpgradeStatus: Upgraded to oneiric on 2011-09-16 (18 days ago)
UserGroups:

Tags:

Revision history for this message

Vincent Zweije (t-vincent-c) wrote on 2011-10-04:

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

Revision history for this message

Apport retracing service (apport) wrote on 2011-10-04: 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.