Description of problem: Evolution stop receiving messages and stuck Demonstration video: https://docs.google.com/open?id=0B0nwzlfiB4aQQ2FJMDBsTG9TRms
Created attachment 665933 [details] evolution backtrace
Created attachment 665939 [details] evolution-addressbook-factory backtrace
Created attachment 665940 [details] evolution-calendar-factory backtrace
Created attachment 665941 [details] evolution-source-registry backtrace
Created attachment 665942 [details] evolution-alarm-notify backtrace
Stuck later again, new video: https://docs.google.com/open?id=0B0nwzlfiB4aQQU5PXzFNbUxBX1U
Created attachment 665966 [details] evolution backtrace
Created attachment 665967 [details] evolution-addressbook-factory backtrace
Created attachment 665982 [details] evolution-calendar-factory backtrace
Created attachment 665983 [details] evolution-source-registry backtrace
Created attachment 665984 [details] evolution-alarm-notify backtrace
Thanks for a bug report. I see the same cause as is in your bug #888172, thus I'm marking this as a duplicate of it. A basic rule on Evolution's quit is that the quit will not happen while there are pending activities in the status bar, or any other pending operations (some are not shown in status bar). P.S.: Feel free to create a script like this: #!/bin/bash FILENAME=/tmp/`date +%Y%m%d-%H%M%S`-$1-bt.txt gdb --batch --ex "t a a bt" -pid=`pidof $1` &>$FILENAME to which you pass one argument only, a process name, and it'll create backtrace of it in /tmp with a date and process name as well. It can be enhanced to get backtraces of all known evolution processes (involving awk or such tool from the `ps ax | grep evolution` command, or just by name them all) like this: #!/bin/bash FILENAME_PREFIX=/tmp/bt-`date +%Y%m%d-%H%M%S` PROCESSES="evolution evolution-addressbook-factory evolution-calendar-factory evolution-source-registry evolution-alarm-notify evolution-user-prompter" for PROC in $PROCESSES; do { if [ "`pidof $PROC`" != "" ] ; then FILENAME=$FILENAME_PREFIX-$PROC.txt gdb --batch --ex "t a a bt" -pid=`pidof $PROC` &>$FILENAME fi }; done
*** This bug has been marked as a duplicate of bug 888172 ***