Bug 128953 - Evolution start crashes with CORBA errors. Same happens with gnome-applets when logging in
Summary: Evolution start crashes with CORBA errors. Same happens with gnome-applets wh...
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution   
(Show other bugs)
Version: 2
Hardware: i686 Linux
Target Milestone: ---
Assignee: Dave Malcolm
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-08-02 01:08 UTC by Gildardo Sanchez
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-02 03:16:21 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Gildardo Sanchez 2004-08-02 01:08:35 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510

Description of problem:
Up2date updated a CORBA component today. After this, Evolution did not
load properly. I saw this reported as a bug, and marked as solved in
2003. However, the thuth is that it is there. After log out, and log
in again, none of the applets in gnome are working. Nothing in the
panel appears as it was before. The error in evolution is 
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'
If there is something wrong in the update, then more people will get
the same problem as soon as they update.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install the latest update from up2date
2.log in for the first kind of error (applets)
3. click on evolution 


Actual Results:  The applets should appear in the menu
Evolution does start after error messages, but does not recover the set up

Additional info:

Comment 1 Gildardo Sanchez 2004-08-02 03:16:21 UTC
If the computer is rebooted, the errors dissapear. 
Maybe it would be convenient to put a message according to this, so
that when the update is complete, the user reboot the computer. Just
as when installing updates of the kernel.

Note You need to log in before you can comment on or make changes to this bug.