GNOME Bugzilla – Bug 678783
[abrt] Crash under e_attachment_set_file_info()
Last modified: 2012-07-13 12:25:12 UTC
Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=834252 [abrt] evolution-3.4.2-1.fc17: gtk_widget_path_copy: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) libreport version: 2.0.10 abrt_version: 2.0.10 backtrace_rating: 4 cmdline: evolution comment: Died during fetching message with attachment form Exchange server (via EWS). crash_function: gtk_widget_path_copy executable: /usr/bin/evolution kernel: 3.4.2-4.fc17.x86_64 time: czw, 21 cze 2012, 12:50:38
+ Trace 230424
Thread 2 (Thread 0x7f30b79d09c0 (LWP 1893))
Thread 1 (Thread 0x7f306e7fc700 (LWP 5113))
On the first look, backtrace's Thread 2 is the main thread, where all UI/gtk functions should be only called, but here Thread 1, a dedicated thread for attachment_load_from_mime_part_thread() calls gtk+ functions in a signal handler after e_attachment_set_file_info().
Created attachment 218711 [details] [review] evo patch for evolution; This avoids any EAttachment::set function call from attachment_load_from_mime_part_thread(), and moves it into e_attachment_load_finish() function, thus the notification on EAttachment properties will be delivered there, which is (usually) in the main thread.
Created commit 76bc1fd in evo master (3.5.4+) Created commit 6da48c7 in evo gnome-3-4 (3.4.4+)