GNOME Bugzilla – Bug 342910
Formatting Message hangs
Last modified: 2008-03-16 21:56:14 UTC
Please describe the problem: Evolution works fine from a fresh start and reads both IMAP and POP accounts and LDAP addressbooks. WIth no obvious trigger the status bar message 'Formatting message (...) hangs and does not go away. There may be multiple 'tabs' of the same message in the status bar at the bottom. At the same time the message preview window freezes on the last message viewed. Messages can only be viewed/previewed by openning a new window. Evolution will not respond to an exit command at this point and hangs with a 'greyed out' screen. To shut down requires 'evolution --force-shutdown' in a terminal Steps to reproduce: 1. sustained regular use 2. 3. Actual results: status bar message 'Formatting message (...) hangs message preview window freezes will not respond to an exit command Expected results: Does this happen every time? eventually yes 30 minutes to an hour after booting when using Other information:
chris, and you please run evolution in gdb? start a terminal window and enter "gdb evolution". then enter "run". after that, evolution starts as normal. when evolution freezes, please go to the terminal window and hit "control + c". after that, enter " thread apply all bt". please post that output here. do you use IMAP or IMAP4rev1 accounts? please only use IMAP. IMAP4rev1 is experimental and deprecated. thanks in advance.
Using only IMAP When evolution crashs gdb returns as follows (evolution-2.6:10566): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution-2.6:10566): camel-WARNING **: camel_exception_get_id called with NULL parameter. [New Thread -1299985488 (LWP 10673)] [New Thread -1335891024 (LWP 10674)] [Thread -1335891024 (LWP 10674) exited] (no debugging symbols found) [Thread -1299985488 (LWP 10673) exited] (no debugging symbols found) [New Thread -1299985488 (LWP 10714)] [New Thread -1335891024 (LWP 10715)] [Thread -1299985488 (LWP 10714) exited] [Thread -1335891024 (LWP 10715) exited] thread_db_get_info: cannot get thread info: generic error (gdb) Quit (gdb) thread apply all bt Segmentation fault
....looks like a memory corruption to me, do you always get a segmentation fault?
/me stoopid. forget the last comment.
Bug 336767 comment 8 has a solution to this problem. It mentions Debian, but I'm running ubuntu (close cousin, eh?) and the work around does indeed work for me.
*** Bug 336821 has been marked as a duplicate of this bug. ***
the reporter in bug #336821 claims that updating has fixed this issue. can we close this bug?
This issue isn't currently fixed in the Dapper release of ubuntu, but it appears that perhaps it is fixed in code. The work around seems good enough with the report that the problem should be fixed as packages are delivered to end users.
Since according to duplicate bug reporter updating has fixed issue, fix is available for this bug. Marking this bug to 'Needinfo' for reporter to update and close this bug once fix is available in 'Ubuntu'.
jeremy, can you please update the status of this bug after you have installed an update? thanks a lot in advance.
Created attachment 68482 [details] MIME email that problem can be seen with I would like to add that I do not seem to experience this problem when I am using my system at home, but the problem shows up at work. What's the difference in my setup? At work, I'm using exchange on the back end (though it seems midly unstable even at the current release, but that's nother story). At home, I use either IMAP or unix spool (using unix spool now; had been using IMAP). When running the work around specified in Bug 336767 comment 8, I'm not able to immediately reproduce this issue. I'm using a sample html formatted message from news-alert@mysql.com to attempt this repro. In the hopes that this problem may be duplicated by importing the email from the mysql team, I have attached it. Some changes were made to protect the innocent servers this message transited.
After an idle delay of approximately one hour, when I returned and clicked on the same message, the system again stayed in a Formatting message (...) state.
maintaining regular updates seems to have addressed the issue. I have now had over a week without any re-occurence of the original bug. Now I am up to Gnome 2.14.2 with 15/06/06 build date. Ubuntu 6.06 . Evo 2.6.1 Thanks all
Apparently it is due to a remote address book (LDAP directory or Exchange Global Address List). See bug 361145 and bug 502665.
I'm also seeing this problem with evolution 2.12.3 Other bugs which may be duplicates of this one are: http://bugzilla.gnome.org/show_bug.cgi?id=361145 http://bugzilla.gnome.org/show_bug.cgi?id=342910 http://bugzilla.gnome.org/show_bug.cgi?id=502665 Seems to be a very common problem. $ rpm -qa | grep evolution evolution-exchange-2.12.3-1.fc8 evolution-exchange-debuginfo-2.12.3-1.fc8 evolution-data-server-1.12.3-2.fc8 evolution-remove-duplicates-0.0.3-1.fc8 evolution-sharp-debuginfo-0.14.0.1-1.fc8 libopensync-plugin-evolution2-0.22-2.fc8 evolution-remove-duplicates-debuginfo-0.0.3-1.fc8 evolution-2.12.3-1.fc8 evolution-webcal-2.12.0-1.fc8 evolution-help-2.12.3-1.fc8 evolution-data-server-debuginfo-1.12.3-2.fc8 syncevolution-0.6-2.fc8 evolution-sharp-0.14.0.1-1.fc8 libopensync-plugin-evolution2-debuginfo-0.22-2.fc8 evolution-python-0.0.4-2.fc8 evolution-python-debuginfo-0.0.4-2.fc8 evolution-webcal-debuginfo-2.12.0-1.fc8 evolution-debuginfo-2.12.3-1.fc8 beagle-evolution-0.2.18-5.fc8
*** This bug has been marked as a duplicate of 361145 ***