Transparent GUI Window Ubuntu 22.04

[0n0n0m0uz]

I recently updated to Ubuntu 22.04 and protonmail bridge window is completely transparent. I have tried uninstalling and the same. I would imagine some of the changes in Ubuntu version may be the culprit.

[ghost]

I am experiencing this as well. The original issue report is obviously low quality, so I will try to provide some additional information:

Expected Behavior

Protonmail Bridge launches with GUI visible in window frame.

Current Behavior

Protonmail Bridge launches with GUI transparent (background wallpaper visible) in window frame.

Possible Solution

Add native Wayland support? This appears to occur at the intersection of electron/wayland and possibly Nvidia?

Steps to Reproduce

Launch Protonmail Bridge with Wayland Windowing System (Possibly with Nvidia Driver?). NOTE! The bridge functions (i.e. I can send and receive emails via Thunderbird, I just can’t access the GUI, because the window is transparent within the frame)

Version Information

2.1.3 (Was also present in previous versions.) I tried the flatpak and the issue is the same. I assume OP is using .deb package, so this issue appears to affect all package types.

Context (Environment)

Fedora 36 Workstation 64-bit Gnome 42 DE Wayland DE (APP WORKS AS EXPECTED UNDER XORG!) Nvidia Display Driver 510.68.02 (this transparent GUI behavior present over multiple driver releases. Unknown if there is a previous driver release that worked with this app, sorry.) Kernel 5.17.5-300.fc36.x86_64 x86_64 (This bug has been present over past kernels as well. I suspect this is an electron/wayland conflict...but what do I know, I'm an end user! [and a paid Proton user])

Please inform what logs would be useful to help diagnose this behavior.

I'll be following this report as a test to see if Proton is actually monitoring and responding to issues. My impression is that for unclear reasons Proton support for Linux is very subpar... Yes, Linux is 2%. If Proton doesn't wish to support Linux, please state that you do not wish to support Linux.

[andrzejsza]

hi @MelReynolds, thanks for the report. of course we're monitoring, even if are not that great with responding 😅 we (the Bridge team) actually spend by far more time on Linux than any other platform but do acknowledge our shortcomings here (from binaries distribution to GUI). We're hoping to give it even more time in the future.

For this particular issue, the problem seems to be somewhat related to NVIDIA GPU. We've got the same report on Fedora 36, also on nvidia.

[ghost]

Thank you @andrzejsza. I got carried away at the end of the issue report. I apologize for being an entitled jerk. I'll work to do better. I believe in Proton's mission and appreciate your work.

[Blookebleep]

I second this issue. I'm using: GNOME: 42.2 Wayland Nvidia Driver: 515.57

Also received this transparent looking window using Wayland which was not a problem using XORG. Seems that this may not have Wayland support or is not falling back too a XORG session using Wayland. Although, I have not tested this on an AMD GPU which has notoriously better driver support. Non-apparent in the Proton VPN application.

No real reason for me to say this here but I just wanna add that this issue seems to be constant.

[jeremy-lilly]

I have this issue as well. I'm using:

Arch Linux Kernel 5.18.11 GNOME 42.2 Wayland Nvidia 515.57 Proton Bridge Flatpak from Flathub

Interestingly, I have a very similar problem using Zoom. This seems like an electron/nvidia/wayland issue.

[BezPowell]

Also seeing this on Fedora Silverblue 36 with propriety nvidia drivers using the Bridge flatpak. Annoying, as it's about the only software application that doesn't work on Wayland now for me.

[bentenjamin]

+1

OS: Fedora release 36 (Thirty Six) x86_64 Host: OMEN by HP Laptop 15-ce0xx Kernel: 5.19.8-200.fc36.x86_64 Uptime: 51 mins Packages: 3405 (rpm), 53 (flatpak) Shell: fish 3.5.0 Resolution: 1920x1080 DE: GNOME 42.4 WM: Mutter WM Theme: Adwaita Theme: Adwaita-dark [GTK2/3] Icons: Adwaita [GTK2/3] Terminal: kitty CPU: Intel i7-7700HQ (8) @ 3.800GHz GPU: NVIDIA GeForce GTX 1060 Mobile 6GB Memory: 6439MiB / 15944MiB

WARN[Sep 14 17:50:23.175] Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.  pkg=frontent/qml
WARN[Sep 14 17:50:24.480] qglx_findConfig: Failed to finding matching FBConfig (8 8 8 8)  pkg=frontent/qml
WARN[Sep 14 17:50:24.480] qglx_findConfig: Failed to finding matching FBConfig (1 8 8 8)  pkg=frontent/qml
WARN[Sep 14 17:50:24.481] qglx_findConfig: Failed to finding matching FBConfig (1 1 8 8)  pkg=frontent/qml
WARN[Sep 14 17:50:24.482] qglx_findConfig: Failed to finding matching FBConfig (1 1 1 8)  pkg=frontent/qml
WARN[Sep 14 17:50:24.483] qglx_findConfig: Failed to finding matching FBConfig (1 1 1 8)  pkg=frontent/qml
WARN[Sep 14 17:50:24.484] qglx_findConfig: Failed to finding matching FBConfig (1 1 1 8)  pkg=frontent/qml
WARN[Sep 14 17:50:24.511] qglx_findConfig: Failed to finding matching FBConfig (8 8 8 8)  pkg=frontent/qml
WARN[Sep 14 17:50:24.512] qglx_findConfig: Failed to finding matching FBConfig (1 8 8 8)  pkg=frontent/qml
WARN[Sep 14 17:50:24.513] qglx_findConfig: Failed to finding matching FBConfig (1 1 8 8)  pkg=frontent/qml
WARN[Sep 14 17:50:24.513] qglx_findConfig: Failed to finding matching FBConfig (1 1 1 8)  pkg=frontent/qml
WARN[Sep 14 17:50:24.514] qglx_findConfig: Failed to finding matching FBConfig (1 1 1 8)  pkg=frontent/qml
WARN[Sep 14 17:50:24.516] qglx_findConfig: Failed to finding matching FBConfig (1 1 1 8)  pkg=frontent/qml
WARN[Sep 14 17:50:24.557] QSGContext::initialize: depth buffer support missing, expect rendering errors  pkg=frontent/qml

[adrihut]

+1

OS: Fedora 36 (x86_64) DE: GNOME 42.5

WM: Mutter WM Theme: Adwaita

GPU: NVIDIA NVIDIA Driver Version: 515.65.01

[andrzejsza]

could you guys try with 2.4.0 (beta) and confirm if that's still a problem?

[ghost]

could you guys try with 2.4.0 (beta) and confirm if that's still a problem?

Yes, 2.4.0 fixes this issue for me! Thank you.

If this solves this issue for others I think this bug is resolved!