After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 619511 - Evolution freeze after connection lost
Evolution freeze after connection lost
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
2.30.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-05-24 12:52 UTC by Angel Abad
Modified: 2010-07-10 03:44 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Trace from launchpad (7.64 KB, text/plain)
2010-05-26 20:39 UTC, Angel Abad
Details

Description Angel Abad 2010-05-24 12:52:24 UTC
In Ubuntu Lucid Aymeric PETIT reported:

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"

Launcpad ref: https://bugs.edge.launchpad.net/evolution/+bug/584906

Thanks!
Comment 1 Vibha Yadav 2010-05-25 10:00:39 UTC
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
Comment 2 Vibha Yadav 2010-05-25 10:05:20 UTC
Might be dup of bug 608327
Comment 3 Vibha Yadav 2010-05-25 13:01:16 UTC
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).
Comment 4 Angel Abad 2010-05-26 20:39:03 UTC
Created attachment 162049 [details]
Trace from launchpad
Comment 5 André Klapper 2010-05-26 22:14:20 UTC
When forwarding bug reports to upstream please first make sure that there is enough information available otherwise it gets noisy here.

The trace completely lacks any debug information. See comment 1.
Comment 6 Fabio Durán Verdugo 2010-07-10 03:44:39 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!