Created attachment 1224528 [details] Screenshot of Evolution I've just upgraded to Fedora 25, and I'm seeing weird rendering issues when running Evolution, as shown in the screenshot. The application seems to be running fine - clicking around suggest it's responding to keyboard and mouse normally - but obviously the UI isn't actually readable. No other application seems to exhibit this behaviour. Video card, since that seems likely to be relevant, is a new Radeon 470...
Oh, and to confirm - this only occurs under Wayland. If I switch back to X11, it runs fine. No idea what Evolution would be doing differently, that all my other apps (Firefox, Chrome, Terminal, Rhythmbox, Nautilus, etc) aren't.
Thanks for a bug report. That's really weird. I would expect some trouble in the preview panel, because there's used WebKit2 (webkitgtk4, which can use different features of the graphics card/drivers), but seeing whole application misdrawn is really odd, because the rest is gtk+ (gtk3). Could you try to run the evolution from a terminal, to see whether it claims anything there, please? As the second try, could you run it like this, please? $ WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
Running from a terminal, nothing gets written. If I run with WEBKIT_DISABLE_COMPOSITING_MODE=1, it works fine. Nothing in the terminal for that case either.
Ah, and your mention of WebKit prompted me to think about what other parts of Gnome use it. And as it turns out, running both Yelp and Epiphany exhibit exactly the same behaviour. Launched from Gnome, or from a terminal without disabling compositing, I get rendering issues identical to those in Evolution. Run from the terminal with WEBKIT_DISABLE_COMPOSITING_MODE=1, they work correctly. Looks like it's a WebKit error. You're right though, it's weird that it affects the entire window, not just the part using WebKit. But thinking on it, this is Wayland, and from what little I know of the subject, the entire "window" (client-side decorations and all) is a single Wayland "surface", and that "surface" will equate more or less directly to some object at the OpenGL/driver level. And I *assume* that WebKit compositing will ultimately be pointing at the same OpenGL object. Some sort of discrepancy over what that common object looks like, maybe? A little more detail I forgot to mention in the original report. The corrupted screen remains static when nothing is interacting with the window - however, the whole window tends to flicker rapidly whenever the mouse pointer moves across it.
Created attachment 1226185 [details] Screenshot of Yelp
Thanks for the update. Evolution itself already received a change which forces not to use the compositing more [1], it's part of the upcoming 3.22.3, change made for upstream bug [2]. I do not know how other applications using webkit2 do that. There's for example also devel-doc, which is using WebKit2. I've no idea whether it uses yelp in the background or not. [1] https://git.gnome.org/browse/evolution/commit/?id=0de465d6a1 [2] https://bugzilla.gnome.org/show_bug.cgi?id=774067
So, it sounds like this isn't actually an Evolution bug, as such, since it affects every WebKit component I can think of testing. Rather than closing it on the basis that a future Evolution release will work around the bug, should it perhaps be moved to a more appropriate component, such as WebKit?
(In reply to Simon Geard from comment #7) > So, it sounds like this isn't actually an Evolution bug, as such, since it > affects every WebKit component I can think of testing. Rather than closing > it on the basis that a future Evolution release will work around the bug, > should it perhaps be moved to a more appropriate component, such as WebKit? We (WebKitGTK+ developers) are aware of the issue.
I just created an upstream bug for it, I didn't find any appropriate (might be I used a wrong search term though): https://bugs.webkit.org/show_bug.cgi?id=165246
*** Bug 1400669 has been marked as a duplicate of this bug. ***
Just FYI, I've installed Fedora updates today, and the problem seems to be gone in all of the affected apps. Among other things, that included the Mesa 13 release, so it's possible that changes at the driver level have fixed things...