Hi, thanks for reporting the bug.

Which version of WebKitGTK are you using?

I am running on a HDPI laptop (scaling = 2), and messages and the composer editor renders fine. I am using  WebKitGTK 2.14, but have noticed something like issue you mention running against WebKitGTK 2.15.

Hi,

getting bitten by this also:

* using arch linux, windows-scaling-factor = 2 (HiDPI)
* updated geary from geary-0.11.3-1 to geary-0.11.3+711+g4e27949d-1

No visible messges any more

* downgraded geary:

messages are visible again.

Cheers,
Max

fyi: webkit on my system:

pacman -Qs webkit
local/epiphany 3.22.6-1 (gnome)
    A GNOME web browser based on the WebKit rendering engine
local/qt5-webkit 5.8.0-1 (qt qt5)
    Classes for a WebKit2 based implementation and a new QML API
local/qtwebkit 2.3.4-4
    An open source web browser engine (Qt port)
local/webkit2gtk 2.14.4-1
    GTK+ Web content engine library
local/webkitgtk 2.4.11-4
    Legacy Web content engine for GTK+ 3

Hey,

thanks for quick response. I'm using ArchLinux too. Here are my versions of webkit GTK:

webkit2gtk 2.14.4-1
webkitgtk 2.4.11-4

It seems that somewhere between 2.14.0 and 2.14.4 there is a problem, right? 

Thanks,
Arek

Yup, I'm running WebKitGTK 2.14.3, so I guess it's a bug introduced in WebKitGTK 2.14.4/2.15?

WebKit bug posted here: https://bugs.webkit.org/show_bug.cgi?id=168180

Either of you two with 2.14.4/2.15 installed please try building geary from master with line 29 of src/client/application/main.vala commented out and let me know if that fixes the issue for you? Ta!

Hi Michael,

I've made a change requested by you (I hope it is correct):

diff --git a/src/client/application/main.vala b/src/client/application/main.vala
index f41d18e5..4a3308bb 100644
--- a/src/client/application/main.vala
+++ b/src/client/application/main.vala
@@ -26,7 +26,7 @@ int main(string[] args) {
     // acceleration, and it is costs a lot in terms of performance
     // and memory:
     // https://lists.webkit.org/pipermail/webkit-gtk/2016-November/002863.html
-    Environment.set_variable("WEBKIT_DISABLE_COMPOSITING_MODE", "1", true);
+//    Environment.set_variable("WEBKIT_DISABLE_COMPOSITING_MODE", "1", true);
 
     GearyApplication app = new GearyApplication();


and it *doesn't help*.

BTW: Here are logs from Geary when starting after build:

[msg] 09:42:49 0,036862 geary-application.vala:241: Geary master~g80441297-dirty prefix=/usr/local exec_dir=/home/kitarek/Pobrane/geary is_installed=false
[deb] 09:42:49 0,034425 client-web-view.vala:132: Failed to load user CSS file:(...) /home/kitarek/.config/geary/user-message.css.. (...)


Furthermore, I made a few tests with different webkit2gtk versions I could downgrade locally:

* webkit2gtk-2.14.2-2-x86_64: messages works and they are visible (everything works as expected)
* webkit2gtk-2.14.3-1-x86_64: message box completely not visible (just email headers) - I've attached another screenshot
* webkit2gtk-2.14.4-1-x86_64: message box visible but not the email content

Created attachment 345558 [details]
Geary message with webkit2gtk-2.14.3 (no message box visible)

(In reply to kitarek from comment #7)
> 
> I've made a change requested by you (I hope it is correct):
> [snip]

That's what I was thinking, yeah. Thanks for testing that and all of the WebKit combinations out, I guess that isn't useful as a workaround for the moment.

I notice that the WebKit bug has been marked as a dupe of: https://bugs.webkit.org/show_bug.cgi?id=168128 which suggests the problem is actually a combination of DRI3 + HDPI scaling-factor = 2, so launching Geary from the terminal using this command might provide a temporary workaround:

  LIBGL_DRI3_DISABLE=1 /path/to/geary

Does this fix the issue when running 2.14.4?

The problem is that every time I'm launching geary from command line (different terminals) the main window isn't showing up -- no matter if I'm adding the environmental variable or not. Obviously via GNOME3 I can invoke an action like "open new window" but I think this creates another process and I'm not sure if the above variable is really referenced/used.

The PID is the same so I hope the test makes sense.

Anyway that variable isn't helping.

As a workaround to use Geary I'm downgrading the webkit version and ignoring it in updates but this is probably not an LTS (= Long Term Solution).

Thanks a lot for assistance!

I just wanted to let you know that in ArchLinux a new version of webkit2gtk (2.14.5-1) arrived which fixes all the visibility issues I had within this ticket. 

Currently I have the following webkit related packages installed:

webkit2gtk 2.14.5-1
webkitgtk 2.4.11-4

Since there is no more work needed from Geary side, I'm closing this ticket.

Thanks for any help!

Thanks for the update, kitarek!