Re: [Evolution] Evo 2.2.1 always 'unexpectedly closed'

["LLLActive GMX Net" <LLLActive GMX Net>]

Hi Andre,

On Fri, 2005-10-14 at 17:17 +0200, Andre Klapper wrote: 
> hi al,
>
> Am Donnerstag, den 13.10.2005, 15:06 +0200 schrieb LLLActive GMail com:
> > I have Evo 2.2.1 Groupware Suite from Novell's Suse 9.3 Pro distro. It
> > suddenly does not close properly. Error Message: "The Application
> > "evolution-2.2" has quit unexpectedly"; " You can inform the
> > developers of what happened to help them fix it. Or you can restart
> > the application right now."
> > Bug Buddy also hangs up (complains that gnome is older than 6 months).
> > Restart works but no clean shutdown. 'Send and Receive' also hangs
> > with 'Waiting' for the pop servers. Where should I start looking. 
>
> as bug-buddy does not work properly, please take a look at the section
> "Debugging Evolution's Crashes" at
> <http://www.gnome.org/projects/evolution/bugs.shtml> and submit the
> "debugging info" (it's called gdb stacktrace or backtrace) - it's
> exactly the same that bug-buddy would do for you.
>
> cheers,
> andre
>
> _______________________________________________
> Evolution-list mailing list
> Evolution-list gnome org
> http://mail.gnome.org/mailman/listinfo/evolution-list

In the mean time I built up an OSS10 with a new Evo 2.4.0. I waited
untill now to see if my problem is solved by the new installation.

I backed up my .evolution directory and restored it in the new system
before starting Evo 2.4.0. It loaded fine and imported everythin; except
the contacts (which I imported as VCards from the backup). The best
restore I experienced in Evo so far!

But, I have the same problem with the '.. quiting unexpectedly'. It
could only be caused by the data directory .evolution that I restored.
That is why I think I have is some relevant new info. Strangely, I have
a sub-directory in the Inbox that I can not delete. It says that it is
not empty, even if there is nothing in it, except for another
sub-directory I created in the past. This sub-dir was inhereted from the
previous system, which had the same problem. How can I delete this
sub-directory? Could it cause the problem?

DEBUGGING:
gdb is installed in OSS10. I run it and then got the following:


########################## START ################
gdb evolution
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "x86_64-suse-linux"...(no debugging symbols
found)
Using host libthread_db library "/lib64/tls/libthread_db.so.1".

(gdb) run
Starting program: /opt/gnome/bin/evolution
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912613807168 (LWP 4965)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
adding hook target 'source'
Setting up initial mail tree
addressbook_migrate (0.0.0)

(evolution:4965): Gtk-CRITICAL **: gtk_widget_hide: assertion
`GTK_IS_WIDGET (widget)' failed
[New Thread 1075841376 (LWP 4997)]

################### END ####################

I noticed that Evo now wanted to start from scratch as if it was run
first time with creating an account. Not knowing what could happen to my
existing installed mails etc., I cancelled the account creation and got:

####### Start 2 ########

[New Thread 1075841376 (LWP 4997)]

Program exited normally.

####### End 2 ##########

Evo started normally again in KDE.

Closing produced the 'closing unexpected' message again.

Thanx for the help.
:-)
Al