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 723888 - After trying to go offline (and failing): Hang when closing (stuck "Retrieving message '166919' in foldername")
After trying to go offline (and failing): Hang when closing (stuck "Retrievin...
Status: RESOLVED DUPLICATE of bug 720197
Product: evolution
Classification: Applications
Component: Mailer
3.10.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2014-02-08 10:30 UTC by André Klapper
Modified: 2015-03-03 11:55 UTC
See Also:
GNOME target: ---
GNOME version: 3.9/3.10


Description André Klapper 2014-02-08 10:30:23 UTC 
Tried to go offline.
After seeing "Retrieving message '166919' in foldername" and "Syncing messages in folder 'foldername' to disk (4% complete)" for more than 12 hours (GMail IMAP+ account), I tried to close Evolution. As nothing happened either after an hour (as expected), I got the pid by
     ps ax | grep evolution
     17398 ?        Sl   225:09 evolution
and then ran
     gdb -p 17398

(gdb) thread apply all bt

+ Trace 233143


(gdb) info registers
eax            0xfffffdfc	-516
ecx            0x4	4
edx            0xf	15
ebx            0xb0e1948	185473352
esp            0xbf8c7194	0xbf8c7194
ebp            0x4	0x4
esi            0x93f1140	155128128
edi            0xb0e1948	185473352
eip            0xb775b424	0xb775b424 <__kernel_vsyscall+16>
eflags         0x200293	[ CF AF SF IF ID ]
cs             0x73	115
ss             0x7b	123
ds             0x7b	123
es             0x7b	123
fs             0x0	0
gs             0x33	51
Comment 1 André Klapper 2014-02-08 10:30:46 UTC 
See also bug 720197
Comment 2 Milan Crha 2015-03-03 11:55:51 UTC 
The same reason as in bug #720197, thus I mark this as a duplicate of it.

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