Bitwarden Flatpak Install Shows just a blank screen this morning about com.bitwarden.desktop HOT 9 CLOSED

Removing the GPU cache folder might be a better workaround:

rm -rf ~/.var/app/com.bitwarden.desktop/config/Bitwarden/Partitions/bitwarden/GPUCache

Source: bitwarden/clients#6732 (comment)

from com.bitwarden.desktop.

I have this issue on Fedora 38, Gnome, Wayland.

I have removed this folder, and it fixed the issue.

rm -rf ~/.var/app/com.bitwarden.desktop/config/Bitwarden/Partitions/bitwarden/GPUCache

from com.bitwarden.desktop.

Workaround: I turned off GPU Acceleration in Flatseal and Bitwarden works. See other issue for details: bitwarden/clients#6732

from com.bitwarden.desktop.

Workaround via terminal:

$ flatpak override --user --nodevice=dri com.bitwarden.desktop

from com.bitwarden.desktop.

This might be yet another manifestation of this issue:
https://discussion.fedoraproject.org/t/chromium-based-browsers-display-garbled-web-pages-after-mesa-is-updated/83438
https://bugs.chromium.org/p/chromium/issues/detail?id=1442633

from com.bitwarden.desktop.

You need to clear the GPU cache:

I have this issue on Fedora 38, Gnome, Wayland.

I have removed this folder, and it fixed the issue.

rm -rf ~/.var/app/com.bitwarden.desktop/config/Bitwarden/Partitions/bitwarden/GPUCache

from com.bitwarden.desktop.

@ghisvail Please don't close this issue. Clearing the cache is just a workaround, not a solution, and will happen again the next time mesa libraries are updates. Also, only a negligible percentage of users will find this workaround.

This needs a proper solution. What about removing GPU acceleration until the problem is resolved? For Bitwarden it's not needed anyway.

from com.bitwarden.desktop.

It's an issue with many Electron apps, not specifically Bitwarden. The issue should be forwarded elsewhere.

What about removing GPU acceleration until the problem is resolved?

Besides, where do I track the "until the problem is resolved" part? So far, I have got no visibility.

from com.bitwarden.desktop.

It's an issue with many Electron apps, not specifically Bitwarden. The issue should be forwarded elsewhere.

Yes, I agree, the core issue is not in Bitwarden, and needs to be solved elsewhere. But Bitwarden users are affected, so we need at least some mitigation until the the problem is resolved. If we rely on people finding this ticket and pruning their cache regularly, we'll have 99% of user base leaving annoyed either at Bitwarden or at Flatpak.

I think dropping --device=dri from the manifest is a very simple thing to do at this moment, with essentially zero drawbacks.

Besides, where do I track the "until the problem is resolved" part? So far, I have got no visibility.

I think the proper upstream bug is this one:
https://bugs.chromium.org/p/chromium/issues/detail?id=1442633

It looks like this got fixed a few weeks back, so hopefully this should be resolved once Electron picks up the fixed Chromium version and then Electron is updated in Bitwarden flatpak, if I understand the deps right?

from com.bitwarden.desktop.