fts.py crashed with DatabaseLockError in __init__(): Unable to get write lock on /home/ron/.local/share/zeitgeist/bb.fts.index: already locked

Bug #898434 reported by sojourner
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zeitgeist (Ubuntu)
New
Undecided
Unassigned

Bug Description

I have no idea what precipitated this crash . I had just quit a root gedit instance , read only no edits made no save .

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: zeitgeist-core 0.8.99~alpha1-1ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-2.5-generic 3.2.0-rc3
Uname: Linux 3.2.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed Nov 30 20:06:49 2011
DuplicateOf: https://bugs.launchpad.net/bugs/896445
ExecutablePath: /usr/share/zeitgeist/fts-python/fts.py
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111123)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: python /usr/share/zeitgeist/fts-python/fts.py
PythonArgs: ['/usr/share/zeitgeist/fts-python/fts.py']
SourcePackage: zeitgeist
Title: fts.py crashed with DatabaseLockError in __init__(): Unable to get write lock on /home/ron/.local/share/zeitgeist/bb.fts.index: already locked
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
sojourner (itsmealso2) 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 this software better. This particular crash has already been reported and is a duplicate of bug #896445, 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
visibility: private → public
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.