Fix pushed to lp:~zeitgeist/zeitgeist/bug727226.
Another outstanding problem is that, when a method fails and triggers
the reconnect, it is run again straight away but it ends up failing
another time. This is something I'll look into fixing once this branch
has been merged (maybe by deferring the call onto the signal handler).
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Python API: Reconnect signals on Zeitgeist restart notification
Status in Zeitgeist Framework:
Bug #673008 fixed the Python API not reconnecting all signals when it
starts the Zeitgeist daemon again after loosing the connection with
it. Now what's missing is doing the same when someone else is
restarting Zeitgeist (ie. by listening to D-Bus's join/leave
Mailing list: https://launchpad.net/~zeitgeist
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp