GNOME Bugzilla – Bug 249352
evolution-wombat process doesn't exit
Last modified: 2003-10-17 10:59:29 UTC
Description of Problem: When Evolution is run and quits, it lefts evolution-wombat and evolution-alarm-notify processes running. When I exit Gnome, evolution-wombat is still running, which causes bonobo-activation-server to still run, which in turn prevents the configuration daemon from starting next time I log in. Killing evolution-wombat manually helps (bonobo-activation-server then exits itself). strace shows that evolution-wombat does a poll() which never ends. Perhaps it shouldn't stay alive at all? Or at least it should exit when I log out. I'm using Gnome-2.4 with GConf-2.4.0.1 and GDM. The gconfd-2 process stays running after I log out but it doesn't cause trouble if Evolution was not run or if I kill evolution-wombat manually. (As a separate issue, sometimes Evolution crashes at start and starting it again hangs until I kill evolution-wombat manually. I'm not filing a bug report about this because it's not repeatable. Anyway, there are other cases when evolution-wombat gets stuck.) Steps to reproduce the problem: 1. Run Evolution and exit. 2. Log out from Gnome. 3. Log in again. Actual Results: The error message says that the configuration daemon could not be started (and font sizes etc. are back the default). Expected Results: The session starts as usual, with no leftovers from the previous session. How often does this happen? Always. Additional Information:
this is either a calendar or addressbook bug. the mailer doesn't know anything about wombat
*** This bug has been marked as a duplicate of 226100 ***