Evolution freeze after connection lost

[Aymeric]

Binary package hint: evolution

I am connected to a wireless AP.
Some time the link is lost, after that evolution is often freezen (95 pourcent).

Now I run evolution from console to kill it with ^C on console I have this only message.

I am connected to only account as OWA.

"$evolution

 Error syncing up the counts"

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: evolution 2.28.3-0ubuntu9
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Mon May 24 12:33:38 2010
ExecutablePath: /usr/bin/evolution
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=fr_FR.utf8
SourcePackage: evolution

[Angel Abad (angelabad)]

In Gnome Bugzilla Vibha Yadav said:

Thanks for the bug report. Unfortunately, that stack trace is not very useful
 in determining the cause of the crash. Could you please install some debugging
packages [1] and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the "details", now
containing way more information. Please copy that stacktrace and paste it as a
comment here. Thanks!

[1] debugging packages for evolution, evolution-data-server, evolution-exchange
and gtkhtml,
 plus debugging packages for some basic GNOME libs. More details can be found
here:

    http://live.gnome.org/GettingTraces/DistroSpecificInstructions

Thanks!

[Angel Abad (angelabad)]

In Gnome Bugzilla Vibha Yadav said:

This is the issue of hang, thus Bug buddy won't pop-up. If you can reproduce it while running under gdb, do "Ctrl-C" and then execute "thread apply all backtrace". This would help in getting better traces if you've already installed debug packages. (see http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for details about how to do this).

[Aymeric (mulx)]

I run evolution trough gdb and get back-trace when it crash.

See attachment.

[Angel Abad (angelabad)]

Thanks Aymeric, posted in Gnome Bugzilla.

[Angel Abad (angelabad)]

Hi, sorry Aimeryc but as you can see in Gnome Bugzilla, this trace is not sufficient. Please install gdb pacakges and check

http://live.gnome.org/GettingTraces/DistroSpecificInstructions

Thanks!

[Aymeric (mulx)]

Evolution re-crash, I have 3 backtrace the 2 first is not probably useful.
I not sure that I have all debugging symbol for the first bt.

[Aymeric (mulx)]

Hi !

Why changing for invalid !? I think that I post enough bt !

Nobody answer to say if it's enough or not and because I don't have my life to post bt I stop....

If you want more bt, just say !

Aymeric :-|

[Angel Abad (angelabad)]

Hi! Its marked as invalid automatically by Bug Watcher, please see:

https://bugzilla.gnome.org/show_bug.cgi?id=619511

From Gnome Bugzilla:

"The trace completely lacks any debug information"

So, please reopen it if you can provide more info.

Thanks!

[Aymeric (mulx)]

Hi!
I provided 3 backtraces with debug package installed (a least in the two last).
Called "second bt" & "third bt"

Bye.

[Jörg Frings-Fürst (jff-de)]

10.04 is not longer supported
change status to invalid (see gnome-Bugs)