Version-Release number of selected component: evolution-3.17.91-1.fc23 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: evolution crash_function: gtk_style_context_get_style_valist executable: /usr/bin/evolution global_pid: 10582 kernel: 4.2.0-1.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_style_context_get_style_valist at gtkstylecontext.c:1863 #1 gtk_style_context_get_style at gtkstylecontext.c:1898 #2 e_web_view_update_fonts at e-web-view.c:2806 #3 e_web_view_init at e-web-view.c:1794 #4 g_type_create_instance at gtype.c:1864 #5 g_object_new_internal at gobject.c:1780 #6 g_object_new_valist at gobject.c:2039 #8 mail_paned_view_constructed at e-mail-paned-view.c:680 #9 g_object_new_internal at gobject.c:1820 #10 g_object_new_valist at gobject.c:2039
Created attachment 1070670 [details] File: backtrace
Created attachment 1070671 [details] File: cgroup
Created attachment 1070672 [details] File: core_backtrace
Created attachment 1070673 [details] File: dso_list
Created attachment 1070674 [details] File: environ
Created attachment 1070675 [details] File: exploitable
Created attachment 1070676 [details] File: limits
Created attachment 1070677 [details] File: maps
Created attachment 1070678 [details] File: mountinfo
Created attachment 1070679 [details] File: namespaces
Created attachment 1070680 [details] File: open_fds
Created attachment 1070681 [details] File: proc_pid_status
Created attachment 1070682 [details] File: var_log_messages
Thanks for a bug report. if I read the backtrace properly, then the crash happened on evolution start. The var_log_messages suggests there happened some sort of memory corruption, maybe a use-after-free, a code reading memory which was already freed. That's only a wild guess. Does this crash each time you try to start evolution, or it crashes only once (or from time to time), please?
No, after this mornings boot evolution starts without crashing.
I forgot: But until I shut down my system yesterday evening Evolution crashes on every attempt to start it.
Was there done any update between yesterday and today? I suspect gtk3 as the place of the crash, but I tried to reproduce with an up-to-date rawhide, also under valgrind, but nothing related was claimed by it.
Yes, today there were a lot of updates from updates-testing but no gtk3 update.
Then I made a wrong guess. Do you think there's more to be done, here? Evolution can start, and most likely an update of some package fixed the issue, while my only guess was gtk3, but it was wrong. I have no other idea of a culprit package.
I don't know. So lets wait a few days if this happens again and if not, close this bug.
Another user experienced a similar problem: This appears to be caused by the Numix GTK theme. It hasn't caused crashes in any other applications so far. It happens as soon as I run evolution, and I didn't run the previous version after installing the theme so I can't tell when it started to be an issue. The theme definitely works in Fedora 22. reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: evolution crash_function: gtk_style_context_get_style_valist executable: /usr/bin/evolution global_pid: 392 kernel: 4.2.1-300.fc23.x86_64 package: evolution-3.18.0-1.fc23 reason: evolution killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
An update: I had recompiled a src rpm that was made for F22. This was not the most recent version of the Numix theme. After pulling the most recent version of the Numix repo, building, and installing the theme manually, I no longer see this error with the theme selected. Seems like an incompatibility with an older version of the theme, but I'm not sure what's causing this error or how it can be avoided with an older theme version.
Another user experienced a similar problem: Click on the Evolution icon, Evolution tries to start and then crashes. reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: evolution crash_function: gtk_style_context_get_style_valist executable: /usr/bin/evolution global_pid: 13936 kernel: 4.2.2-300.fc23.x86_64 package: evolution-3.18.0-1.fc23 reason: evolution killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
The evolution tries to read from the Theme: gtk_style_context_get_style ( context, "link-color", &link, "visited-link-color", &visited, NULL); both as a pointer to a GdkColor structure. These style properties are defined on the GtkWidget itself, as GdkColor-s. Thus the way evolution works with them is correct, even the properties as such are deprecated in gtk+. This seems to be related to certain themes, as I understand it, thus the issue can be partly with the theme and maybe also the desktop environment.
An Arch user in #evolution reported this, using gtk 3.18.0 on Cinnamon with a theme called "greybiance2". But "gsettings get org.gnome.desktop.interface gtk-theme" says "Adwaita".
(In reply to Andre Klapper from comment #25) > An Arch user in #evolution reported this, using gtk 3.18.0 on Cinnamon with > a theme called "greybiance2". > But "gsettings get org.gnome.desktop.interface gtk-theme" says "Adwaita". And the same user reported that after an update of gtk3 to 3.18.2 evolution started without issues. Could you update to gtk3 3.18.2+ too, please? To verify, whether it's it.
A user of an upstream bug [1] reported that an update to gtk3 3.18.2 fixes the crash, thus I'm closing this as such. [1] https://bugzilla.gnome.org/show_bug.cgi?id=756508