Blank cryptomator window when running inside container on ChromeOS

[t0rv1c]

I am using Cryptomator on Linux Debian 10 (Crostini).
Since using version 1.5.1, I can't interact with the application window as it's blank. Everything works fine on 1.5.0. 1.5.2 doesn't fix the issue. I believe something changed with the UI between 1.5.0 and 1.5.1. Could it be "Migrated to JDK 14 and GitHub Actions"?
Thanks!

[overheadhunter]

Could it be "Migrated to JDK 14 and GitHub Actions"?

Possibly. How does the "blank window" look like? Is it comparable to #1049?

[t0rv1c]

@overheadhunter No, it is not comparable because there is no frame to be seen, it's all white but I can tell I can kind of interact with the window (using tabs to select close for example). I don't really know what keyboard keys I can use to select and open the vault but I think it's possible. Anyway I am also using a Windows PC and I found another even bigger bug (just posted). Again, I wish I had beta-tested this version and I would have probably refrained from upgrading in the end...

[ghost]

@t0rv1c Do you know what desktop environment you have installed?

@overheadhunter Debian switched from X to Wayland display server/compositing for default gnome desktops, i think the others stayed on X

[overheadhunter]

Debian switched from X to Wayland display server/compositing for default gnome desktops, i think the others stayed on X

That is an important hint. There have been a couple of issues with wayland reported already. Yet, I don't know any fix yet, as this needs to be fixed upstream.

[infeo]

Another important information is missing: The issue appears when Cryptomator runs inside a linux container on ChromebookOS.

I am using Cryptomator on Linux Debian 10 (Crostini).

The codename of Debian 10 is buster. A short google search for "Crostini" shows:

Crostini is the umbrella term for making Linux application support easy to use and integrating well with Chrome OS."

[t0rv1c]

Remember that the issue only appeared after 1.5.0. 1.5.0 still shows the window correctly and from 1.5.1 on it doesn't anymore...

[overheadhunter]

Remember that the issue only appeared after 1.5.0. 1.5.0 still shows the window correctly and from 1.5.1 on it doesn't anymore...

In that case, this might be a duplicate (with different symptoms) of #1167.

Can you try if this workaround works for you?

[no-response]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.