are you using a gtk theme that makes gtk widgets look/act like Qt/kde
widgets? That's what it looks like from the errors printed to the
console. I would suggest disabling gtk themes and seeing if that
resolves the issue. I know at one point, a lot of KDE users submitted
bugs about Evolution crashing when they used some sort of gtk theme that
used a kludgy hack to make gtk draw to the screen using the Qt libs
which would often cause segfaults and/or fun X errors.

On Tue, 2005-07-19 at 13:23 -0700, Ross Boylan wrote:
> Every time I start evolution it crashes almost immediately.  Using
> E2K_DEBUG produces no useful output.  However, .xsession-errors shows
> -------------------------------------------------
> X Error: BadAccess (attempt to access private resource denied) 10
>   Major opcode:  2
>   Minor opcode:  0
>   Resource id:  0x3400005
> DCOPReply<>: cast to 'QStringList' error
> DCOPReply<>: cast to 'QString' error
> evolution-shell-Message: Killing old version of evolution-data-server...
> es menu class init
> adding hook target 'source'
> evolution-shell-Message: Killing old version of evolution-data-server...
> es menu class init
> adding hook target 'source'
> --------------------------------------------------------
> 
> I had evolution running, but it crashed as I was changing to the task
> list (as I recall).  My Cyrus IMAP server was also having problems at
> the time; my /var filled up and made a mess.  I think all those issues
> are resolved.
> 
> evolution 2.2.2-4 on Debian/GNU Linux 2.4.27, running testing (which
> is just a little past the recent release).
> 
> I'm running under KDE 3.3.2, XFree 4.3.0.
> 
> I'd appreciate assistance fixing, or at least debugging, this problem.
> 
> Thanks.
> Ross Boylan
> _______________________________________________
> evolution maillist  -  [email protected]
> http://lists.ximian.com/mailman/listinfo/evolution
> 

_______________________________________________
evolution maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/evolution

Reply via email to