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 269441 - Consistent hang while "Scanning for changed messages" or "Fetching summary information" when connecting across internet
Consistent hang while "Scanning for changed messages" or "Fetching summary in...
Status: RESOLVED DUPLICATE of bug 331096
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.0.1
Other All
: Normal major
: 2.0.4
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks: 270418
 
 
Reported: 2004-11-13 09:55 UTC by Mike Ely
Modified: 2006-02-16 10:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Per discussion on gimpnet, GDB output for the evolution-exchange-storage process, using "thread apply all bt" (14.40 KB, text/plain)
2004-11-13 09:56 UTC, Mike Ely
Details
Additional gdb outputfile for evolution-data-server process using same as above (7.29 KB, text/plain)
2004-11-13 09:57 UTC, Mike Ely
Details
Another attempt at running the debugger (23.58 KB, text/plain)
2004-11-16 08:56 UTC, Mike Ely
Details

Description Mike Ely 2004-11-13 09:55:06 UTC
Description of Problem:
With multiple (pop, IMAP, exchange) accounts configured, evolution will
hang when switching between accounts at one of the places in summary. 
Killing the exchange database process results in imap or pop accounts
becoming readable, but results in evolution crash when attempting to switch
back to exchange account.

I'd say I have to deal with this problem about 80% of the time from home...
about 5%-10% of the time when connecting at work (direct LAN connection to
exchange server at work).
Comment 1 Mike Ely 2004-11-13 09:56:48 UTC
Created attachment 44389 [details]
Per discussion on gimpnet, GDB output for the evolution-exchange-storage process, using "thread apply all bt"
Comment 2 Mike Ely 2004-11-13 09:57:53 UTC
Created attachment 44390 [details]
Additional gdb outputfile for evolution-data-server process using same as above
Comment 3 Mike Ely 2004-11-16 08:56:02 UTC
Created attachment 44396 [details]
Another attempt at running the debugger
Comment 4 Mike Ely 2004-11-16 08:58:28 UTC
The most-recent gdb output is as close as I can get to a full gdb of
just the connector, as I was told that my previous attempt did not get
full backtrace.  I obtained this one by starting the exchange storage
process independently from evolution, then launching evolution around
it.  I'm really not sure this is how it's supposed to work - if anyone
can give me pointers on how to get a full backtrace of just the
connector, I'll be happy to do that and post it here (unless of course
the attached is sufficient to diagnose the bug).
Comment 5 Sarfraaz Ahmed 2004-11-29 18:53:01 UTC
This stack looks very similar to 68762
Comment 6 Sarfraaz Ahmed 2005-02-09 08:07:45 UTC
Can you please give the exact steps to reproduce this ? Like, i have
these accounts configured, and when i perform this particular steps in
sequence, i get this behaviour. Also, please elaborate more on
"switching between accounts"
Comment 7 Mike Ely 2005-02-09 18:03:50 UTC
Steps to reproduce are as follows:

1) Create an account to an Exchange server, and an account to a
separate server, IMAP or POP - doesn't matter.  What does seem to
matter is that the server connections need some latency - when I
connect over my office LAN I don't have these problems.

2) Read your email in the non-exchange account.  Then click on the
Inbox for your Exchange account (This is what I meant by "switching
between accounts").

About half the time I do step 2 here, I'll get the hang.  I really
don't know what is different between the times I get the hang and when
I don't - I'm not doing anything different.

Bug occurs with stock SuSE 9.1 packages/updates, ULB-Gnome packages
for SuSE 9.1 (www.usr-local-bin.org), and ubuntu warty and hoary.
Comment 8 Sarfraaz Ahmed 2005-02-10 08:48:09 UTC
Hmm, this sounds like some race condition somewhere. Do you have debug
build or built connector from sources ? We could get the symbol
information if you either of those. Even if you dont have, can you
start evolution-exchange in gdb and take some snapshots of what it
doing [ for every few seconds ] while it is hung ? Atleast we would
know what it is hanging on.
Comment 9 Sushma Rai 2006-02-16 10:21:51 UTC
looks similar to 322901 and 331096.

Mike Ely, which is your libsoup version?

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