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 628232 - Evolution hang on exit
Evolution hang on exit
Status: RESOLVED DUPLICATE of bug 628515
Product: evolution-data-server
Classification: Platform
Component: general
2.30.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
evolution[imapx]
Depends on:
Blocks:
 
 
Reported: 2010-08-29 06:21 UTC by Ruchir Brahmbhatt
Modified: 2012-04-27 09:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ruchir Brahmbhatt 2010-08-29 06:21:54 UTC
OS: opensuse 11.3 x86_64
Evolution: 2.30.3 (From Gnome:Stable repo)
Account: Gmail IMAP+

Happens: Sometimes (At least once a day)

Steps to reproduce:
1. Start evolution.
2. Do some normal operations for long time.
3. Exit by ctrl+q.

Expected result:
Evolution should store IMAP updates and exit.

Actual result:
Evolution doesn't close. Status says "Storing inbox".

Backtrace:



Comment 1 Akhil Laddha 2010-08-30 05:08:47 UTC
not sure if it's related to bug 624705
Comment 2 Ruchir Brahmbhatt 2010-08-30 05:21:23 UTC
Yes it looks related. I experienced just now. Network interrupted and then I can no longer close evolution, it just hang. I had to kill it.
Comment 3 Jean-François Fortin Tam 2010-09-28 19:32:26 UTC
Duplicate of bug #628515 or vice versa? 628515 does give an indication of what might be happening though.
Comment 4 Ruchir Brahmbhatt 2010-09-30 05:59:00 UTC
May be its same. As if before closing evolution, if I switch folder(which saves inbox state) then it closes cleanly. But if it has to save state at the time of closing, it hangs.
Comment 5 Milan Crha 2012-04-27 09:12:27 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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