GNOME Bugzilla – Bug 731344
Reproducible freeze trying to read a specific email with LaTeX file attachment
Last modified: 2014-06-10 14:38:32 UTC
evolution-3.10.4-2.fc20.i686 evolution-data-server-3.10.4-3.fc20.i686 webkitgtk-2.2.7-1.fc20.i686 webkitgtk3-2.2.7-1.fc20.i686 Tried to open an email marked as unread in a GMail IMAP+ Inbox (which I had read before so I know what's in there). That email has several LaTeX files attached (content of one LaTeX file can be seen in thread 1, to my surprise). Thread 8 shows stuff from my other IMAP+ account configured. No idea in which account thread 2 is, probably same as thread 1. 0xb776d424 in __kernel_vsyscall () Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.3800.2-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace (gdb) thread apply all bt
+ Trace 233673
(gdb) info register eax 0xfffffdfe -514 ecx 0xbffe147c -1073867652 edx 0xbffe14fc -1073867524 ebx 0x33 51 esp 0xbffe13fc 0xbffe13fc ebp 0xb77278bc 0xb77278bc esi 0x0 0 edi 0xbffe1474 -1073867660 eip 0xb776d424 0xb776d424 <__kernel_vsyscall+16> eflags 0x293 [ CF AF SF IF ] cs 0x73 115 ss 0x7b 123 ds 0x7b 123 es 0x7b 123 fs 0x0 0 gs 0x33 51 (gdb)
Cool, it's reproducible. "Parsing message" is shown for a moment in the status bar. To reproduce, the foo.bib file attached to the message starts with the following lines: @inproceedings{MockusLongTermContributors, author = {Zhou, Minghui and Mockus, Audris}, booktitle = {Proceedings of the 2012 International Conference on Soft\-ware Engi\-neering}, title = {What Make Long Term Contributors: Willingness and Opportunity in {OSS} Community}, year = {2012}, series = {ICSE 2012}, pages = {518--528}, publisher = {IEEE Press}, address = {Piscataway, NJ, USA}, note = "Also available at \url{http://mockus.us/papers/willingness.pdf}", location = {Zurich, Switzerland}, }
I believe you face bug #724909, thus I marked this as a duplicate of it. *** This bug has been marked as a duplicate of bug 724909 ***