Created attachment 604654 [details] backtrace evolution Description of problem: Do not see a list of letters at the time of the receipt of mail (IMAPX) Gmail Demonstration: https://docs.google.com/open?id=0B0nwzlfiB4aQZlI5X05icmtXWGc
What means this? mikhail@u3s3 ~]$ cat /tmp/evolution-2012-08-16.2.txt /usr/bin/evolution (deleted): No such file or directory. Thread 1 (process 2142): #0 0xb60c333e in ?? () #1 0x0001fd00 in ?? () #2 0x0003a300 in ?? () #3 0x0001fd00 in ?? () #4 0x0003a300 in ?? () #5 0x0000041b in ?? () #6 0x0001fd00 in ?? () #7 0x0003a300 in ?? () #8 0x00020900 in ?? () #9 0x0003bf00 in ?? () #10 0x0928e390 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Created attachment 604683 [details] backtrace evolution
Created attachment 604686 [details] backtrace evolution
Created attachment 604687 [details] backtrace evolution
Created attachment 604689 [details] htop screenshot
$ rpm -qa | grep evolution | sort evolution-3.4.4-1.fc17.i686 evolution-data-server-3.4.4-1.fc17.i686 evolution-data-server-debuginfo-3.4.4-1.fc17.i686 evolution-debuginfo-3.4.4-1.fc17.i686 evolution-NetworkManager-3.4.4-1.fc17.i686
Created attachment 604691 [details] Evolution screenshot
Something lock message list rendering process and get high CPU load.
Created attachment 604694 [details] backtrace evolution
Thanks for a bug report. (In reply to comment #1) > What means this? > > mikhail@u3s3 ~]$ cat /tmp/evolution-2012-08-16.2.txt > /usr/bin/evolution (deleted): No such file or directory. > > Thread 1 (process 2142): > #0 0xb60c333e in ?? () > #1 0x0001fd00 in ?? () > Backtrace stopped: previous frame inner to this frame (corrupt stack?) It seems like you updated evolution to 3.4.4 while other was still running. From the video, screen-shots and backtraces: I see quite many activities being run and shown in the status bar. The backtraces show one thread reading data from the (probably GMail) server, and other threads waiting for it being finished. That explains so many activities, and probably also the inability to update message list.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.