Python API: Reconnect signals on Zeitgeist restart notification
Bug #727226 reported by
Siegfried Gevatter
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Zeitgeist Framework |
Fix Released
|
Medium
|
Siegfried Gevatter | ||
Bug Description
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 notifications).
Related branches
lp:~zeitgeist/zeitgeist/bug727226
- Mikkel Kamstrup Erlandsen: Approve
-
Diff: 104 lines (+33/-17)1 file modifiedzeitgeist/client.py (+33/-17)
| Changed in zeitgeist: | |
| importance: | Undecided → Medium |
| milestone: | none → 0.8.0 |
| status: | New → Triaged |
Revision history for this message
| Siegfried Gevatter (rainct) wrote | #1 |
| Changed in zeitgeist: | |
| assignee: | nobody → Siegfried Gevatter (rainct) |
| milestone: | 0.8.0 → 0.7.1 |
| status: | Triaged → Fix Committed |
| Changed in zeitgeist: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
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).