Meanwhile this issue persist even after reboot, either the original cause for the blockage being removed after a reboot was not deterministic, but random or a dependency changed and reintroduced a bug.
> Could it be that you at one point opened a desktop session as root or started > a desktop application which potentially uses Zeitgeist with sudo? I had my eye on it for some time now and I didn't figure out why a `zeitgeist` daemon is started by root. I wouldn't bother with it. If `diodon` relies on certain conditions (be that only one `zeitgeist` daemon process running by a specific user or the `zeitgeist` database being unlocked), then these conditions have to be checked before every action taken. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1405525 Title: database is locked error prevents Diodon from adding items to or clearing history To manage notifications about this bug go to: https://bugs.launchpad.net/diodon/+bug/1405525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
