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

[sojourner]

not doing anything inparticular I had just opened a root gedit window with sudo when the box poped up gedit functiond normaly .

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: zeitgeist-core 0.8.99~alpha1-1ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-1.3-generic 3.2.0-rc2
Uname: Linux 3.2.0-1-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Fri Nov 25 18:14:14 2011
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
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
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:

[Launchpad Janitor (janitor)]

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

[openick (openick)]

This problem occurred when I opened gedit to edit /var/lib/apt/lists Gedit popped up with an error message in red to say that it is a directory. It was then that the error report was generated

[Tadeáš Pařík (pariktadeas)]

I can confirm it. This problem occurred when I wanted to edit /etc/apt/apt.conf.d/50unattended-upgrades

[Otto Kekäläinen (otto)]

I was browsing available wallpapers in desktop settings as it crashed and the automatic bug system notified there was an error with fts.py.

I'm running Ubuntu 12.04 with all the latest updates installed.

[Sasa Paporovic (melchiaros)]

By me it was on:

sudo nautilus
nautilus to var/crash
openup an crash(read determined to root, because of system crash) with double click(gedit).
On closing gedit I see zeitgeist crash report laying arround in var/crash in the still opened nautilus.

Thats all.

[Tadeáš Pařík (pariktadeas)]

Today I only opened terminal and received this bug, I did not edit anything in /etc/apt/... So let's few seconds after the start of the system, no other action done.

[Stephen Ewen (ewenste)]

Got the crash when simply running sudo gedit -s for a standalone root instance.

[brian baker (brian-m-baker)]

got crash just by opening up the terminal app !
running ubuntu 12.04 with all latest updates!

[José Marques (jm-domus)]

same here
inside sudo gedit, editing grub.

[mfauzirahman (mfauzirahman)]

it happen right away after login. Before I start anything

[Joost Van Durme (joostvandurme)]

Same here, only logged in to Unity, then immediately got fts.py crash error.

[jerrylamos (jerrylamos)]

sudo gedit /etc/apt/sources.list and got his error, precise updated to 29 Jan, 3.2.0-12-pae

Jerry

[Laura Czajkowski (czajkowski)]

Logged into precise and I immediately get this error of a crash

[Alan Pope 🍺🐧🐱 🦄 (popey)]

Isn't this a result of people using sudo to run graphical applications, which we (in support circles) tell people not to do?

https://help.ubuntu.com/community/RootSudo#Graphical_sudo

"You should never use normal sudo to start graphical applications as Root. You should use gksudo (kdesudo on Kubuntu) to run such programs. gksudo sets HOME=~root, and copies .Xauthority to a tmp directory. This prevents files in your home directory becoming owned by Root. (AFAICT, this is all that's special about the environment of the started process with gksudo vs. sudo). "

[Tadeáš Pařík (pariktadeas)]

@Alan,

it could be answer for one part of this problem, e. g. if I wanted to edit something in /etc/apt/... However in the previous versions this problem did not occur. The second part - now time to time I receive this error opening terminal only (without editing or using sudo for graphical applications) and some users also when they want to log into the system...

[Colin Law (colin-law)]

@Alan Pope: It happens at other times also, but even if it did only happen when using sudo gedit (for example) it still should not crash. In fact if you look at your quote it suggests that the only difference between sudo and gksudo is the setting of HOME and copying .Xauthority, there is no way that not doing that should cause a crash.

[kobe (florin-kobe)]

got this bug while using vlc

[McVries (mcvries)]

A few seconds after boot while opening terminal.

[Simon Clements-Hawes (simon-hawes)]

I got this whilst running sudo gedit /var/log/Xorg.0.log

[phillipude (2phillipsmail)]

The bug info appeared when I attepted to report another bug at https://bugs.launchpad.net

[Alexandre Jodoin (cacalex)]

I have this as well, a few seconds after boot.
I'm not trying to open anything. It just happen...

[David Barth (dbarth)]

The Python version of the FTS extension is going away next week, says mrh3.

[Jacovenko (jacovenko-gmail)]

while doing the update

[kevinchou (kevinchou-c-gmail)]

same here...

[userdce (userdce)]

happened on restart

[Juan Carlos (arareka-ha)]

Same here, after login.

[Alexx (ag-cdo)]

I've had this a number of times after login. Nothing open or opening.

[Michal Hruby (mhr3)]

The fts.py was a temporary solution and is no longer part of zeitgeist package.