Comment 4 for bug 559350
Revision history for this message
| Mikkel Kamstrup Erlandsen (kamstrup) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Looking quickly at fixinf this on the ZG side as well... I am actually afraid that this is impossible to fix inside Zeitgeist :-S
We dispatch the monitor DBus calls asynchrously, and the bug is somehow picked up very low in the stack in an async callback before it reaches Zeitgeist. Indeed I can see no Zeitgeist code in the stack trace. Also, we are actually passing in an error handler to DBus which *ought* to be invoked on errors, but apparently not, since that should simply result in a warning printed on stdout.