From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
Description of problem:
Select evolution from menu and start program
(first time or subsequent invocation).
Error message pops up, and after a while the
application loads, but does not contain any of
its default contents.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.start evolution from menu
2. close error message, and wait for
3. program to load
Actual Results: program throws up this error message:
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'
closing error dialog, the program contiunes to load, but
without it's default components (folders and other objects).
Expected Results: program should load and create / show default
contents (folders, and other objects).
System: Athlon Thunderbird 1.0 Gb. Severn beta (RH 9.0.93)
Video subsystem: 3D Labs (32 Mb) nVidia card
Viewsonic 17 monitor.
N.B. Nvidia drivers are NOT installed.
Created attachment 93203 [details]
screenshot of loaded application
Are you running in GNOME or KDE?
The failure occurs in the Gnome desktop with Severn. Have not yet tried under KDE
Hmmm, and other GNOME apps start correctly?
Does anything odd show up in the terminal if you try to start evolution from there?
when started from a console prompt the same thing occurs. (See attachment). The
actual error pop-up is created as four instances stacked up on each other. The
console output is therefore:
(evolution:23620): evolution-shell-WARNING **: Could not start any startup wizard!
(evolution:23620): evolution-shell-CRITICAL **: file e-shell-startup-wizard.c:
line 781 (e_shell_startup_wizard_create): assertion `data->corba_wizard !=
Created attachment 93206 [details]
Note the error dialog actually occurs *four* times, and has to be clicked that
many times for the splash screen to go away.
Do you still see this with test2?
I remember having the same problem with test2, but feel like it's gone
in test3. Would someone verify?
This is fixed in Fedora Core Test 3, and (of course) in Fedora Core 1.
I respectfully submit that this bug be marked as closed.