Comment 131 for bug 151536

Please disable automatic startup of "evolution alarm notifier" until this is fixed!

Some people like me are maintaining large LTSP environments and this damn thing screws up the hole system!

* When people log out, there are left over processes.
* They are unable to login again until I kill these processes.
* Alarm Notifier consumes all CPU

I attached a ps axu showing lots of user processes left over after logout. Non of the users listed was logged in, when this file was created. Pay special attention to users 1526, 1528 (names were to long to display) and haasd. Most of their processes did not stop on logout.

They can not log in anymore now! Until I get my hands on and kill their stuff.

The other users show the usual suspects:
scheidlc 17439 0.0 0.2 5340 2216 ? S 11:42 0:00 /usr/lib/libgconf2-4/gconfd-2 12
scheidlc 7864 0.0 0.2 31992 3048 ? Ssl May06 0:00 /usr/lib/bonobo-activation/bonobo-activation-server --ac-activate --ior-output-fd=16
scheidlc 7926 0.0 0.5 42448 5724 ? Sl May06 0:00 /usr/lib/evolution/evolution-data-server-2.22 --oaf-activate-iid=OAFIID:GNOME_Evolution_DataServer_CalFactory:1.2 --oaf-ior-fd=22

This bug goes hand in hand with bug #90258. Two different problems, yes. But the same source.

Disabling Evolution Alarm Notifier solved this problem on my Laptop.
Having certain calendars enabled in Evolution especially the Birthday and Weather stuff seems to trigger some misbehaviour too, especially on the logout front.

I vote for getting rid of evolution all together. But as a quick fix, disable Evolution Alarm Notifier by default!

System info:
LTSP: 1 AMD K7 CPU (32bit)
Laptop: Some 32bit Celeron CPU pre DualCore

It would be so much easier and more accurate if I could just point you to the HW profiles of my systems, which could be attached to my launchpad profile if Canonical would fund and implement an idea outlined here:

http://brainstorm.ubuntu.com/idea/1497/
https://bugs.launchpad.net/malone/+bug/3382