GNOME Bugzilla – Bug 694439
deadlock while retrieving/displaying new mail message
Last modified: 2013-02-22 12:12:52 UTC
Hi encountered a deadlock in Evolution (without CPU hogging/busy waiting). The mail view was open, and I had previously added new appointments to my Google online account. Then I switched to a new email and Evolution started retireving the message. It never got displayed, and Evolution did not respond any longer to any user interaction. set height 0 (gdb) info threads Id Target Id Frame 8 Thread 0x7f794ba31700 (LWP 3481) "dconf worker" 0x00007f795ceca303 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 7 Thread 0x7f794b230700 (LWP 3482) "gdbus" 0x00007f795ceca303 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 6 Thread 0x7f79490ca700 (LWP 3483) "gmain" 0x00007f795ceca303 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 5 Thread 0x7f79488c9700 (LWP 3484) "evolution" 0x00007f795ceca303 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 4 Thread 0x7f79177c3700 (LWP 3500) "evolution" pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 3 Thread 0x7f7916fc2700 (LWP 3501) "evolution" pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 2 Thread 0x7f78cd53c700 (LWP 3507) "evolution" pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:215 * 1 Thread 0x7f794cf829c0 (LWP 3477) "evolution" pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 (gdb) thread apply all bt full
+ Trace 231544
Thread 1 (Thread 0x7f794cf829c0 (LWP 3477))
_g_boolean_var_ = <optimized out> status = <optimized out> (gdb)
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 674885 ***