[Bug 1405525] Re: failure of clearing history and adding item due to Failed to clear items: GDBus.Error:org.gnome.zeitgeist.EngineError.DatabaseError: engine.vala:392: SQL Error: 5, database is locke

2015-01-03 Thread Oliver Sauder
As I cannot reproduce the problem I can only guess - most likely are there several zeitgeist-daemon or zeitgeist-fts running which are locking the database. Can you check the following: ps -ef | grep zeitgeist copy the output and then kill all the processes. See whether it works - if it does the

[Bug 1405525] Re: failure of clearing history and adding item due to Failed to clear items: GDBus.Error:org.gnome.zeitgeist.EngineError.DatabaseError: engine.vala:392: SQL Error: 5, database is locke

2014-12-27 Thread Oliver Sauder
This is a zeitgeist issue which is trying to access a locked database. Logging out Unity and logging in usually fixes this issue. Can you reproduce this issue though in anyway? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1405525] Re: failure of clearing history and adding item due to Failed to clear items: GDBus.Error:org.gnome.zeitgeist.EngineError.DatabaseError: engine.vala:392: SQL Error: 5, database is locke

2014-12-27 Thread Karl-Philipp Richter
Is there a way to unlock the zeitgeist database without logging out and in (I won't do that for the next days, maybe weeks, I guess)? I can only guess whether the issue persists accross reboot, maybe it reappears systematically very soon right after logging in. After reading your reply I feel