After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 769441 - Breeze theme makes evolution crash in gtk3
Breeze theme makes evolution crash in gtk3
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Themes
3.20.x
Other Linux
: Normal critical
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2016-08-02 16:04 UTC by Jonathan Ryshpan
Modified: 2018-04-15 00:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Crash backtrace (12.69 KB, text/plain)
2016-08-02 16:04 UTC, Jonathan Ryshpan
Details
Crash backtrace #2 (16.77 KB, text/plain)
2016-08-10 01:25 UTC, Jonathan Ryshpan
Details
Crash backtrace #3 (18.10 KB, text/plain)
2016-08-10 01:45 UTC, Jonathan Ryshpan
Details
Crash backtrace + Debug Log (23.48 KB, text/plain)
2016-08-21 17:56 UTC, Jonathan Ryshpan
Details

Description Jonathan Ryshpan 2016-08-02 16:04:46 UTC
Created attachment 332579 [details]
Crash backtrace

Frequent crashes in the evolution mail-reader have been traced to gtk.  (I assume evolution uses gtk3.)  The crashes happen under the Breeza theme and not under Adwaita.

Here's the setup:

GTK Themes
    GTK2 Theme: Breeze
    GTK3 Theme: Breeze
    Font: Cantarell 14

Icon Themes
    Cursor Theme: Adwaita
    Icon Theme: Breeze
    Fallback Theme: Hicolor

System:
    Hardware: 4-cpu true intel
    Fedora-24 with all updates installed
    KDE Frameworks 5.24.0
    Evolution 3.20.4

A gdb backtrace is attached.
Comment 1 Matthias Clasen 2016-08-02 16:11:06 UTC
I don't see an actual crash in that stacktrace fragment.
What makes you think this is tied to the theme you are using ?
Comment 2 Jonathan Ryshpan 2016-08-02 18:42:34 UTC
>I don't see an actual crash in that stacktrace fragment.
A good point.  I'll run evolution under gdb again and provide more info.

>What makes you think this is tied to the theme you are using?
I changed themes from Adwaita to Breeze just before the crashes started happening.  The crashes usually happen after I've scrolled one of the windows.  The scrollbars are a little flaky and keep appearing and disappearing, not just "as they ought to", depending on focus, but in a jittery way, sometimes causing unexpected interactions with the GUI.  You can see more in the thread on the Evolution mailing list with subject
    [Evolution] More on Crashes
starting on 7/29.  See:
    https://mail.gnome.org/archives/evolution-list/2016-July/msg00134.html
continuing into August.
Comment 3 Jonathan Ryshpan 2016-08-10 01:25:16 UTC
Created attachment 333035 [details]
Crash backtrace #2
Comment 4 Jonathan Ryshpan 2016-08-10 01:27:29 UTC
Crash backtrace #2 has a better backtrace, which shows a crash.
Comment 5 Jonathan Ryshpan 2016-08-10 01:45:59 UTC
Created attachment 333036 [details]
Crash backtrace #3

Another run, another crash at the same place.
Comment 6 Jonathan Ryshpan 2016-08-21 17:56:37 UTC
Created attachment 333830 [details]
Crash backtrace + Debug Log

Some experimentation shows that when this conditional breakpoint:
    break gtk_css_gadget_queue_allocate if gadget->parent->qdata!=0
is hit, evolution always crashes.  I have not been able to figure out what this means, or even exactly what is the instruction provoking the crash.  Any hints will be very welcome.

The attached Crash backtrace + Debug Log has been edited to show the gdb commands producing the output.
Comment 7 Jonathan Ryshpan 2016-09-14 20:31:27 UTC
Setting the environment variable
    GTK_OVERLAY_SCROLLING=0
seems to stop the crashes.  I have run evolution for about a day and a half since making this change to evolution's start procedure without a crash.
Comment 8 Matthias Clasen 2018-02-10 05:13:21 UTC
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 9 Matthias Clasen 2018-04-15 00:00:38 UTC
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new