Thanks for a bug report. What is the version of the WebKitGTK, please? It's webkit2gtk3 package.

@mcatanza I do not recall, is this due to the sandbox or graphics drivers or anything else? Or was the cause identified at all?

There's no sandbox in RHEL 8. Most likely a problem with graphics drivers, indeed. You can confirm by running with WEBKIT_DISABLE_COMPOSITING_MODE=1, which will probably dodge the bug.

Assuming I'm correct about that: for any realistic hope of resolution, it will need to be reported upstream on WebKit Bugzilla, WebKitGTK component. Things that would be good to do:

 * Try reproducing with a newer distro, e.g. Fedora 37. If the bug only happens on RHEL 8, then it's not going to be worth investigating.
 * Install epiphany (not provided in RHEL), navigate to webkit://gpu, and copy the entire output into upstream bug report

> Install epiphany (not provided in RHEL),

But um, only do this if the bug occurs the same in the newer distro, e.g. Fedora 37. Don't want to mix webkit://gpu output from different distros in the same upstream bug report.

webkit2gtk3-2.36.7-1.el8.x86_64(In reply to Milan Crha from comment #1)
> Thanks for a bug report. What is the version of the WebKitGTK, please? It's
> webkit2gtk3 package.

webkit2gtk3-2.36.7-1.el8.x86_64

> 
> @mcatanza I do not recall, is this due to the sandbox or graphics
> drivers or anything else? Or was the cause identified at all?

I don't have any info about the cause, just the symptom. It must be a regression from some time, though, because I had created Google accounts in the past. In fact, this one had just had its credentials expire and I was trying to renew them but couldn't get the login window. 

This is an nVidia graphics card (Quadro K620) with xorg-x11-drv-nouveau-1.0.15-4.el8.1.x86_64 as the driver.

(In reply to Michael Catanzaro from comment #3)
> > Install epiphany (not provided in RHEL),
> 
> But um, only do this if the bug occurs the same in the newer distro, e.g.
> Fedora 37. Don't want to mix webkit://gpu output from different distros in
> the same upstream bug report.

Does not occur in Fedora 37 (at least with Intel graphics).

Oh, Nvidia graphics card is very relevant. You really need to test Fedora on the same machine. (You can use a live image: there's no need to actually install Fedora.) I bet you'll hit the same problem with Fedora on the Nvidia graphics machine. There are no WebKitGTK graphics developers who use Nvidia graphics, so it's very common for it to be broken, and bugs may take a very long time to be fixed because upstream developers won't be able to reproduce. Intel and AMD graphics are much better supported.

We *might* be able to interest graphics developers at Red Hat if you're a Red Hat customer and create a support ticket to attach to this bug. But should still create a WebKit Bugzilla bug too.

OK Does not seem to occur on the machine at issue with Fedora 37 live image.

Will try with proprietary nVidia drivers.

Works with proprietary nVidia drivers.

In that case, I suppose this was fixed sometime between RHEL 8 and Fedora 37. But who knows what changed. :/

Mesa was recently rebased in RHEL 8.8 - see https://bugzilla.redhat.com/show_bug.cgi?id=2117178 - can you please try to downgrade mesa to its previous version - mesa-22.1.5-2.el8 or similar?

(In reply to Tomas Popela from comment #10)
> Mesa was recently rebased in RHEL 8.8 - see
> https://bugzilla.redhat.com/show_bug.cgi?id=2117178 - can you please try to
> downgrade mesa to its previous version - mesa-22.1.5-2.el8 or similar?

mesa-22.1.5-2.el8 is what I tested and reproduced, so that would rule out the problem with XShm in Mesa.

(In reply to Michael Catanzaro from comment #6)
> Oh, Nvidia graphics card is very relevant.

I can reproduce on el8 on intel the same - This happens with a Wayland session (default) but not on Xorg.

Same as comment 0, the "Google Account" window remains blank, the content of the web page to log into the Google account doesn't show up.

(In reply to Olivier Fourdan from comment #11)
> I can reproduce on el8 on intel the same - This happens with a Wayland
> session (default) but not on Xorg.
> 
> Same as comment 0, the "Google Account" window remains blank, the content of
> the web page to log into the Google account doesn't show up.

Oh wow, very interesting! So not a problem with Nvidia after all, huh.

There's a pretty decent chance that this problem is https://bugs.webkit.org/show_bug.cgi?id=238513. If so, it should be fixed in the WebKitGTK 2.38.2 build that should land in CentOS Stream 8 momentarily. This build depends on libwpe and wpebackend-fdo to provide hardware-accelerated graphics, so the graphics stack is quite different.

You can check by running gnome-control-center in a terminal and looking for any error messages that print when displaying the online accounts panel. This bug results in the error messages:

EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
Cannot create EGL context: invalid display (last error: EGL_SUCCESS)

If you see those, then it's *probably* fixed in this upcoming build.

(In reply to Michael Catanzaro from comment #13)
> […]
> 
> EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
> Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
> 
> If you see those, then it's *probably* fixed in this upcoming build.

You're spot on, I do get those errors!

So note that once this is fixed, you'll still probably be blocked by Google due to https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/157. But at least the web content should load.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: webkit2gtk3 security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:2834