GNOME Bugzilla – Bug 213121
Wombat does not exit when Evolution does
Last modified: 2013-09-10 14:02:36 UTC
I just downloaded the latest CVS changes, and built and installed everything (gal, gtkhtml and evolution). When I restarted Evo, I checked for new mail, read a couple of messages, deleted one, and then exited ( I have auto-empty-trash enabled). I found that wombat did not exit. Here is the backtrace from the stranded wombat process:
+ Trace 12052
I find that this is 100% reproducible.
Still a problem, miles? IIRC, some refcounting issues were fixed here on monday or tuesday...
I'll check. I am running Windoze now.
Yes, I can still reproduce this will all the changes through October 25th.
I've got a change to wombat/pas/pcs that displays the list of active backends in each of PAS/PCS on SIGUSR2, and it seems that when the wombat sticks around there are references to the tasks and default calendar left over. Once I get gnome cvs to cooperate others will be able to use this to see what's around when wombat is hung. in the meantime, reassigning to evolution-calendar-maintainers.
Those "stale references" are not stale at all; they come from the alarm daemon which *does* keep your calendar and tasks folders open in the Wombat. Marking this as a dupe of #11984. *** This bug has been marked as a duplicate of 211984 ***