This should be fixed in GTK+ 3.22.8, though I haven't confirmed it personally.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.