Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 563

Summary: Evolution Mail Settings Broken
Product: Gentoo Linux Reporter: Tom Hoffman <hoffman>
Component: [OLD] GNOMEAssignee: Grant Goodyear (RETIRED) <g2boojum>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: High    
Version: 1.0 RC6 r14   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Tom Hoffman 2002-02-06 16:19:42 UTC
I've installed and compiled Gentoo 1.0 R6 twice on my Duron system, and 
everything works until I get to Evolution (which I've never really gotten to 
work very well on other systems either, but I'd love to get it syncing with my 
Palm).

When I go to the inbox, then Tools > Mail Settings, I get "Application 
"evolution-mail" has crashed due to a fatal error."  I then get a second error 
that says "The Evolustion component that handles folders of type "mail" has 
unexpectedly quit.  You will need to quit Evolution and restart in order to 
access that data again."  

When I look at the error messages sent to the terminal, I see 

Gtk-WARNING **: gtk_signal_disconnect_by_data(): could not find handler 
containing data (0x8149200)

evolution-shell-WARNING **: Error changing interactive status of componenet 
OAFIID:GNOME_Evolution_Mail_ShellComponet to FALSE -- 
IDL:CORBA/COMM_FAILURE:1.0

I'm not doing anything wacky with optimizations or whatever.  My use list has:

pda java cups arts tex bonobo slang readline gpm berkdb gdbm tcpd pam libwww 
ssl nls mitshm perl python esd gif sdl vorbis ogg gnome gtk X qt kde motif 
opengl mozilla

Thanks!
Tom Hoffman
Comment 1 Daniel Robbins (RETIRED) gentoo-dev 2002-02-06 18:31:25 UTC
Which evolution ebuild did you use?  I'm forwarding this bug to Grant who may be
able to point you in the right direction.
Comment 2 Grant Goodyear (RETIRED) gentoo-dev 2002-02-07 10:08:37 UTC
For palm support 1.0-r5 still needs to be used.  

The workaround for evolution-mail crashing is, after installing, start up evo
and then immediately shut it down.  When you restart evo everything should
work correctly.  See bug #10

*** This bug has been marked as a duplicate of 10 ***