I haven't look further into it, *BUT* zeitgeist should handle .Quit() being called multipletimes properly, means: it should not crash. We also have to check how ZeitgeistEngine.close() behaves in this cases.
Reasons for .Quit() being called are for example that two clients try to quit the daemon at about the same time. And for the dbus methods in .Quit which are raising the errors: it is always possible for the connection (e.g. the SessionBus) to drop the connection to ZG before we want to quit. (I haven't further investigate on this, but it seems clear to me looking at the dbus docs) In short: zeitgeist should not crash in .Quit() unless something like storing data in the engine goes terribly wrong. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/807950 Title: zeitgeist-daemon crashed with LookupError in remove_from_connection(): <_zeitgeist.engine.remote.RemoteInterface at /org/gnome/zeitgeist/log/activity at 0xb74ee2cc> is not exported at a location matching (None,None) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/807950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
