Having done an emerge -u world today I can no longer get Evolution to start cleanly. I get four popup windows displayed Cannot activate component OAFIID:GNOME_Evolution_Mail_ShellComponent : The error from the activation system is: Unknown CORBA exception id: 'IDL:omg.org/CORBA/INV_OBJREF:1.0' Cannot activate component OAFIID:GNOME_Evolution_Addressbook_ShellComponent : The error from the activation system is: Unknown CORBA exception id: 'IDL:omg.org/CORBA/INV_OBJREF:1.0' Cannot activate component OAFIID:GNOME_Evolution_Calendar_ShellComponent : The error from the activation system is: Unknown CORBA exception id: 'IDL:omg.org/CORBA/INV_OBJREF:1.0' Cannot activate component OAFIID:GNOME_Evolution_Summary_ShellComponent : The error from the activation system is: Unknown CORBA exception id: 'IDL:omg.org/CORBA/INV_OBJREF:1.0' And then evolution appears with no folders displayed other than the local ones and the message "(No folder displayed)". Reproducible: Always Steps to Reproduce: 1. Launch evolution :-( Actual Results: See above
Having looked at what I actually picked up today I noticed I hadn't picked up a new evolution so thinking it might just need re-compiling against something I had picked up I tried: emerge -C evolution emerge evolution but to no avail, it still does it. Fishing about some more I saw libbonobo in the list of things I did get today (2.6, from 2.4.3 presumably) and a search for 'ALL evolution libbonobo' the bug list threw up bug 52606 which seems to be reporting the same symptoms. However I have no /tmp/orbit-* directories, the deletion of which was a suggested fix I think if I read the bug thread correctly.
Oh, and in case it's of any use, here's and 'emerge info' output Portage 2.0.50-r9 (default-x86-1.4, gcc-3.3.3, glibc-2.3.3.20040420-r0, 2.4.22-gentoo-r2) ================================================================= System uname: 2.4.22-gentoo-r2 i686 AMD Athlon(tm) XP 1800+ Gentoo Base System version 1.4.16 distcc 2.13 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=i686 -funroll-loops -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/moz illa/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=i686 -funroll-loops -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://gentoo.mirror.sdv.fr http://www.die.unipd.it/pub/Linux/distributions/gentoo-sources/ ftp://mirror.pudas.net/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alsa apm arts avi berkdb crypt cups encode esd foomaticdb gdbm gif gnome gphoto2 gpm gtk gtk2 imlib java jpeg kde ldap libg++ libwww mad mikmod motif mozilla mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png postgres python qt quicktime readline sdl slang spell ssl svga tcpd truetype x86 xml2 xmm s xv zlib"
Oh yes, and another data point: I have just (like in the last week or so) upgraded this machine from a twin Celeron based motherboard to a new one with an AMD XP2400 on it. I'm a bit worried when I see I've still got '-march=i686' - is that valid with this processor?
you should also not be in a session. The fact that those dirs do not exist is problematic in itself, cause afaik those are needed for proper orbit behaviour.
OK. I shut down X completely, which I'm assuming is what you meant by not being in a session. Then, when I looked in /tmp those directories did exist (I swear they didn't before!). I deleted them. Evolution now launches fine. I don't really understand why that worked but thanks for your help in steering me in the right direction.
*** Bug 59418 has been marked as a duplicate of this bug. ***
*** Bug 59858 has been marked as a duplicate of this bug. ***
