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 778518 - Preview and Email Windows show blank content
Preview and Email Windows show blank content
Status: RESOLVED NOTGNOME
Product: evolution
Classification: Applications
Component: Composer
3.22.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2017-02-12 02:50 UTC by wompy
Modified: 2017-02-16 10:07 UTC
See Also:
GNOME target: ---
GNOME version: 3.21/3.22


Description wompy 2017-02-12 02:50:37 UTC 
Arch Linux
Gnome 3.22.2
webkitgtk-2.4.11-4
wayland-1.12.0-1
xorg-server-1.19.1-2

Since today I can't see  the content of my emails any more. The preview windows just shows white space. When I open an email, the content/body section turns black and white afterwards, not showing any text.
Sometimes the area stays black and turns white after clicking it.
Comment 1 turbochris 2017-02-13 02:04:48 UTC 
Same problem here with Arch, same version numbers.

Latest webkitgtk update causes the issue.

I rolled back to webkit2gtk-2.14.3-1 and it fixed the problem - not sure about other implications of rolling back this package though.
Comment 2 Milan Crha 2017-02-13 09:30:47 UTC 
Thanks for a bug report and the solution. Due to that I'm closing this, because it's an Arch issue and/or WebKitGTK+ issue (something broken with the 2.14.4 update).
Comment 3 Milan Crha 2017-02-13 10:04:15 UTC 
Just a note, I tried with 2.14.4 on Fedora 25 and I do not see there this issue. My messages (the few I tried) are shown fine, both GNOME Shell on X.org and Wayland.
Comment 4 Michael Catanzaro 2017-02-13 15:15:53 UTC 
It's https://bugs.webkit.org/show_bug.cgi?id=168128. We'll do a new release ASAP.
Comment 5 turbochris 2017-02-15 22:55:54 UTC 
I can confirm it is fixed with updated webkit2gtk-2.14.5-1 package.
Comment 6 Milan Crha 2017-02-16 10:07:25 UTC 
Thanks for the confirmation.