GNOME Bugzilla – Bug 571577
Error while Storing folder 'INBOX'
Last modified: 2010-05-22 08:22:39 UTC
Please describe the problem: I was asked to report this bug on this forum by Pedro Villavicencio <pedro@ubuntu.com> descriptions of how to reproduce, and a workaround, are both to be found here: http://www.mail-archive.com/desktop-bugs@lists.ubuntu.com/msg250529.html Steps to reproduce: 1.I logged in to my regular Ubuntu 8.10 box from another linux box (SuSE 10.3) using ssh -X. I ran evolution in remote XTerm mode for a couple of days (I was having issues with the video on the main box). 2. On the remote box, the shell I used to start the remote XWindow session reported some errors (maybe about a hundred) of two kinds: 3. (evolution:5533): camel-local-provider-WARNING **: Expected a From line here, didn't get it. SO recovering.... I got about 30 of those, and (evolution:5533): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed I got about 90 of those in the screen rollback summary from the remote shell history. Actual results: Now, when I switched back to my Ubuntu HH box, evolution is extremely slow and cpu-intensive, showing the error message described in the above thread: Error while Storing folder 'INBOX' Expected results: normal behaviour? Does this happen every time? I believe so Other information: I think it has to do with how evolution performs when run as a remote terminal through ssh -X
I love being able to help in this small wayis
what is the exact version of your evolution ? Can you please try out current stable 2.24.4 ?
https://bugs.launchpad.net/evolution/+bug/183136 is the launchpad bug and one user suggest the issue happens on corrupted mbox cases using 2.24
Could you please try to regenerate the summary, see https://bugs.launchpad.net/evolution/+bug/183136/comments/40
This version is no longer maintained, which means that it will not receive any further security or bug fix updates. The current stable GNOME and Evolution version is 2.30. Can you please check again whether this issue still happens in Evolution 2.28 or 2.30 and update this report by adding a comment and changing the "Version" field? Thanks a lot. Again thank you for reporting this bug and we are sorry it could not be fixed for the version you originally used here. Without feedback this report will be closed as INCOMPLETE in 6 weeks.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!