GNOME Bugzilla – Bug 788218
Stuck showing "Retrieving message "12345" in "whatever@example.com : INBOX/subfolder"
Last modified: 2017-09-27 13:25:01 UTC
(I cannot remember if I already filed this, sorry!) evolution-3.24.5-1.fc26.x86_64 evolution-data-server-3.24.6-1.fc26.x86_64 is stuck showing "Retrieving message "17077" in "whatever@example.com : INBOX/wmfall" forever in the status bar. Even after switching to offline mode: $:acko\> gdb -p 2786 GNU gdb (GDB) Fedora 8.0.1-26.fc26 Attaching to process 2786 [New LWP 2792] [New LWP 2793] [New LWP 2794] [New LWP 2795] [New LWP 2802] [New LWP 2829] [New LWP 2830] [New LWP 2831] [New LWP 2834] [New LWP 2850] [New LWP 2851] [New LWP 24593] [New LWP 25346] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x00007f0626cd7acd in poll () at ../sysdeps/unix/syscall-template.S:84 84 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) (gdb) thread apply all bt full
+ Trace 238006
rax 0xfffffffffffffdfc -516 rbx 0x562adaa07660 94742056564320 rcx 0x7f0626cd7acd 139664397531853 rdx 0x56 86 rsi 0x6 6 rdi 0x562adcf3b0b0 94742095573168 rbp 0x6 0x6 rsp 0x7ffe4450fa60 0x7ffe4450fa60 r8 0x7 7 r9 0x562adca1bf00 94742090202880 r10 0x562adabc9100 94742058406144 r11 0x293 659 r12 0x562adcf3b0b0 94742095573168 r13 0x56 86 r14 0x7f06313bfb80 139664572545920 r15 0x7 7 rip 0x7f0626cd7acd 0x7f0626cd7acd <poll+45> eflags 0x293 [ CF AF SF IF ] cs 0x33 51 ss 0x2b 43 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 (gdb) list 79 #else 80 81 /* This is a "normal" system call stub: if there is an error, 82 it returns -1 and sets errno. */ 83 84 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) 85 ret 86 T_PSEUDO_END (SYSCALL_SYMBOL) 87 88 #endif (gdb)
Thanks for a bug report. There is one thread calling camel_folder_get_message_sync() which also calls camel_service_connect_sync() and it's waiting for the connection to be finished or rejected. This doesn't happen for some reason. I do not know why yet. It also happened in the past, like yours bug #764044 (as you said), but also bug #742167, which described the very same issue with different circumstances. *** This bug has been marked as a duplicate of bug 764044 ***