GNOME Bugzilla – Bug 267512
Message preview pane sometimes stops working
Last modified: 2013-09-10 14:04:09 UTC
Please fill in this template when reporting a bug, unless you know what you are doing. Description of Problem: Sometimes, the message preview pane gets stuck displaying a particular message. I can click on other messages, other email accounts, delete messages, etc. but no matter what the preview pane will show the same message. Clicking Reply on the selected message will work for the selected message, even if the preview pane is still showing the "stuck" message. The only solution is to restart evolution. I cannot reliably reproduce this, but it happens a couple times a day. I have both IMAP and exchange accounts, but it seems to happen with either equally.
Is this a known issue? If not, what can I do to help debug this?
get a backtrace of all threads. run evolution in gdb and ctrl-c it when it happens and do "thread apply all bt". its probably gpg checking signatures or something.
Ok, I'll let you know what I find. Thanks!
Ok, here goes: Program received signal SIGINT, Interrupt. [Switching to Thread -151152736 (LWP 14414)] 0x410007a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 (gdb) thread apply all bt
+ Trace 50945
Thread 17 (Thread -177525840 (LWP 19401))
Thread 11 (Thread -167035984 (LWP 2918))
Thread 10 (Thread 39693232 (LWP 14426))
Thread 9 (Thread 50183088 (LWP 14427))
Thread 8 (Thread 74750896 (LWP 14428))
Thread 7 (Thread 85240752 (LWP 14430))
Thread 6 (Thread 121605040 (LWP 14432))
Thread 5 (Thread 97848240 (LWP 14433))
Thread 4 (Thread 111115184 (LWP 14455))
Thread 3 (Thread 132094896 (LWP 14457))
Thread 2 (Thread -155751504 (LWP 14471))
Thread 1 (Thread -151152736 (LWP 14414))
I waited a couple more seconds, switched to my exchange account (the message the preview pane is stuck on is from my imap account), and did another thread dump: (gdb) cont Continuing. Program received signal SIGINT, Interrupt. 0x410007a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 (gdb) thread apply all bt
+ Trace 50946
looks like its hanging looking up the sender name in the addressbook. it may be related to exchange connector to, although i don't think so from that trace. as a workaround, try turning off 'load images only if sender in addressbook' in the html mail settings page. before you do that, can you try also getting a backtrace of evolution-data-server's threads too? e.g. gdb /opt/gnome2/libexec/evolution-data-server-1.0 pid where pid is the pid of the evolution-data-server process, and the /opt/gnome2/... path is the path to evolution-data-server-1.0 then ctrl-c and the same backtrace command.
*** bug 264440 has been marked as a duplicate of this bug. ***
Here's the new thread dump for evolution-2.0: Program received signal SIGINT, Interrupt. 0x410007a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 (gdb) thread apply all bt
+ Trace 50960
Thread 13 (Thread 29359024 (LWP 9689))
Thread 12 (Thread 49392560 (LWP 9690))
Thread 11 (Thread 67029936 (LWP 9691))
Thread 10 (Thread 90684336 (LWP 9693))
Thread 9 (Thread 101174192 (LWP 9695))
Thread 8 (Thread 111664048 (LWP 9696))
Thread 7 (Thread 130943920 (LWP 9697))
Thread 6 (Thread 77519792 (LWP 9702))
Thread 5 (Thread -155591760 (LWP 9705))
Thread 4 (Thread -166765648 (LWP 9736))
Thread 3 (Thread -177255504 (LWP 9737))
Thread 2 (Thread -193664080 (LWP 9795))
Thread 1 (Thread -151152736 (LWP 9684))
At the same time, here's evolution-data-server-1.0: Program received signal SIGINT, Interrupt. 0x410007a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 (gdb) thread apply all bt
+ Trace 50961
Thread 3 (Thread 27257776 (LWP 14417))
Thread 2 (Thread 78490544 (LWP 14444))
Thread 1 (Thread -151129984 (LWP 14416))
contacts guys: i think its in the e_book_get_contacts call. this is a duplicate isn't it?
Looks exactly the same as bug 261850. NotZed: feel free to move to Connector.
*** bug 270575 has been marked as a duplicate of this bug. ***
This bug is confirmed to be present in 2.0.3 This bug has also been reported to Debian BTS: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=274912 The report includes a sample message and some other extra information.
since evolution 2.0.x is not maintained/patched anymore, moving all target milestones at least to 2.2.x. sorry for the noise.
Do you still face this. This happens for some particular messages, do you find some kind of pattern in the messages on which it stops working. Also get me the terminal messages by running evolution and evolution-data-server from terminal.
I don't get this anymore. I'm on Evolution 2.4.2.1.
So can this be closed ??
Closing this bug as it is not reproducible, Please re-open if you see this issue again. Thanks.