After upgrade to gnome-2.4, i recognized that evolution don't start, indeed I rebooted the machine for other purposes several times. Because of the trouble with gcc I decided to rebuild evolution. The symptom: It hangs after the splash screen. And when I retry it don't even show the splash screen. With a strace I saw that it hangs when it tries to open a file under /tmp/orbit-kjsdfh so I shut down the whole thing, deleted all files in tmp and tried it again, without success. The solution: After killing evolution I saw two processes: xxxxx 23058 0.0 2.3 25140 5912 ? S 12:48 0:00 /usr/libexec/evolution/1.4/evolution-wombat --oaf-activate-iid=OAFIID:GNOME_Evolution_Wombat_InterfaceCheck --oaf-ior-fd=39 xxxxx 23060 0.0 2.2 23852 5812 ? S 12:48 0:00 /usr/libexec/evolution/1.4/evolution-alarm-notify --oaf-activate-iid=OAFIID:GNOME_Evolution_Calendar_AlarmNotify_Factory --oaf-ior-fd=41 I killed them and then the I could start evolution again :-) Reproducible: Always Steps to Reproduce: 1. 2. 3.
my guess would probably be that the old wombat processes are still using the old ORBit2/bonobo which got confused after the upgrade. I guess this is a one off thing, i can't imagine us killing evolution processes in a gnome ebuild. thanks for reporting the fix though, i'm sure some people will find it useful.
