GNOME Bugzilla – Bug 711513
Viewing particular email hangs entire desktop
Last modified: 2013-11-06 16:55:22 UTC
Created attachment 259042 [details] Bad email This seems serious enough that I hope I can be forgiven for reporting a bug in "obsolete" 3.8.5. I'm subscribed to the Epiphany mailing list, and when I attempt to view the particular message [1] in Evolution, not only does Evolution reproducibly (tried three or four times) hang, it also hangs the rest of my desktop. I cannot even switch TTYs to see what's up, and must hold the power button to shut down. I've never seen this happen with Evolution before. [1] https://mail.gnome.org/archives/epiphany-list/2013-November/msg00002.html This could be a WebKit issue since I've hit similar behavior with Epiphany before, but as this is reproducible I figure I should report it here. The email (downloaded from gmail.com using "show original" since I can't get to it with Evolution) that causes this is attached. I see the following in my journal; dunno how much is relevant, if any. I guess 12:46 was probably before the hang. Nov 05 12:46:15 victory-road gnome-session[1487]: (evolution:2127): Gtk-WARNING **: EAttachmentBar 0x306a090 is mapped but not visible Nov 05 12:46:15 victory-road gnome-session[1487]: (evolution:2127): Gtk-WARNING **: EAttachmentBar 0x306a090 is mapped but not visible Nov 05 12:46:15 victory-road gnome-session[1487]: (evolution:2127): Gtk-WARNING **: EAttachmentBar 0x306a090 is mapped but visible=0 child_visible=1 parent GtkBox 0x31a0510 mapped=1 Nov 05 12:46:15 victory-road gnome-session[1487]: (evolution:2127): Gtk-WARNING **: EAttachmentBar 0x306a090 is mapped but not visible Nov 05 12:46:15 victory-road gnome-session[1487]: (evolution:2127): Gtk-WARNING **: EAttachmentBar 0x306a090 is mapped but visible=0 child_visible=1 parent GtkBox 0x31a0510 mapped=1 Nov 05 12:47:47 victory-road gnome-session[1487]: camel-Message: but uidvalidity changed Nov 05 12:48:12 victory-road gnome-session[1487]: camel-Message: but uidvalidity changed
*** This bug has been marked as a duplicate of bug 711532 ***