GNOME Bugzilla – Bug 710171
[abrt] EShellTaskbar: Gtk+ functions called out of the main thread
Last modified: 2013-10-18 14:23:38 UTC
Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1018870 Version-Release number of selected component: evolution-3.10.0-1.fc20 Additional info: reporter: libreport-2.1.8 backtrace_rating: 4 cmdline: evolution crash_function: _gtk_css_value_ref executable: /usr/bin/evolution kernel: 3.11.4-302.fc20.i686+PAE Core was generated by `evolution'. Program terminated with signal SIGSEGV, Segmentation fault.
+ Trace 232614
Thread 7 (Thread 0xb57ff900 (LWP 2800))
Thread 1 (Thread 0xa52ffb40 (LWP 7000))
The problem is that the crashing thread (in the backtrace Thread 1) calls gtk+ functions, but it's not the main thread (it's the Thread 7 in the backtrace), where gtk+ functions ought to be called.
Created attachment 257644 [details] [review] evo patch for evolution; I cannot reproduce this, also I tried to delete messages in an EWS account, but this patch provides a general solution which makes sure that EShellTaskbar does UI operations only in the main/UI thread, which is how it should be. I believe this is easier than to chase for every single place where to add any idle postponing.
Created commit 431d718 in evo master (3.11.1+) Created commit a7f61d2 in evo gnome-3-10 (3.10.2+)