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

[trollbasen]

Binary package hint: apt-xapian-index

After i logging in to Desktop Edition

Sorry, you don't have 3d support, install it for
your graphic hardware to get Unity or please
reboot and select 'Classic session' at startup.

X.Org X Server 1.9.99.901 (1.10.0 RC 1)
Release Date: 2010-12-06
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-28-xen i686 Ubuntu
Current Operating System: Linux nattynarwhal 2.6.37-12-generic-pae #26-Ubuntu SMP Wed Jan 5 19:00:12 UTC 2011 i686
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.37-12-generic-pae root=UUID=a8b83714-63a5-4898-8cfd-aefe341a13d7 ro quiet splash vt.handoff=7
Build Date: 12 January 2011 03:14:12PM
xorg-server 2:1.9.99.901+git20110111.6358a600-0ubuntu0chris5 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.21.4

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: apt-xapian-index 0.41ubuntu2
ProcVersionSignature: Ubuntu 2.6.37-12.26-generic-pae 2.6.37
Uname: Linux 2.6.37-12-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sat Jan 22 13:14:18 2011
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100803.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --update -q
ProcEnviron:
 LC_MESSAGES=sv_SE.utf8
 LANG=sv_SE.UTF-8
 LANGUAGE=sv_SE:sv:en_GB:en
 PATH=(custom, no user)
 SHELL=/bin/bash
PythonArgs: ['/usr/sbin/update-apt-xapian-index', '--update', '-q']
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
UserGroups: fuse

[Apport retracing service (apport)]

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 #684037, 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.