Thanks Tasos for this additional feedback. It is certainly not a good thing that zeitgeist-daemon needs to be started during build which of course can cause issues as in your case. Something I have noticed in the past as well. I now split integration tests where Zeitgeist is needed and unit tests so this error during build is not happening again see Bug #1471438
What the original cause of this issue is, is still unclear to me. I also had zeitgeist-daemon running as root and my user without any problems. It is not good that zeitgeist-daemon is started as root in any case - but this is not necessary a cause of Diodon as every other application depending on Zeitgeist can issue starting of this daemon. All in all is this a Zeitgeist issue. I haven't reported this yet though as unfortunately I have not been able to create an example where it can be reproduced which would be needed for the Zeitgeist team to fix it. -- 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
