-
Notifications
You must be signed in to change notification settings - Fork 269
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Element desktop starts with blank screen #1074
Comments
Same on Linux Mint 21.1 Cinnamon |
I had the same exact symptom as described in this issue and saw #1029 (comment) which also fixed it for me. I would say this issue here is the same as #1029. |
Same issue here on Manjaro. I've been fixing it slightly different.
This seems to happen whenever |
Chromium upstream is probably working on a fix https://bugs.chromium.org/p/chromium/issues/detail?id=1442633 Meanwhile, deleting the The issue as I understand: Whenever mesa updates from one version to another (major/minor/release/patch), it can introduce internal code changes that make the Chromium/Electron's existing GL shader cache incompatible with newer mesa. Chromium calculates a shaderprefixkey from the GPU driver info to check whether it needs regenerating (ie. if the driver mesa changed versions) https://source.chromium.org/chromium/chromium/src/+/refs/heads/main:components/viz/host/gpu_host_impl.cc;l=415;drc=4a0c2a8e5a4de735817463162218bbf84aa2bd74 But sometimes even minor patch level changes can have breaking changes that might cause the shaderprefixkey to remain the same but the actual cache to become incompatible. Thus chromium won't regenerate the cache and show the above error due to the incompatibility. |
Thank you, that helped. I did not have |
In some cases when somebody installed Element before renaming, can see files in
|
Thanks! That fixed it for me. 😀 I hope that it's okay that I spread the word around a bit in similar issues. |
Release notes for Element v1.11.36 can be found [here](https://github.com/vector-im/element-desktop/releases/tag/v1.11.36). Includes a security fix for CVE-2023-37259. More details can be found [here](GHSA-c9vx-2g7w-rp65). The Mesa shader cache is disabled as workaround for Element starting with a blank screen. More details about this issue can be found [here](element-hq/element-desktop#1074).
This issue has reached my NixOS installation, now. The workaround from above worked for me, too. I didn't even have to sing out and back in again. I just had to launch it once with the mesa cache disable like so: |
I have to open it every time with |
The prefix MESA_SHADER… only sets this value for the single invocation of the command behind it, so it's not surprising that you have to use it every time. You could try to delete the contents of |
For me on NixOS it was |
And for Flatpak, because they put things in different directories, I did: cd $HOME/.var/app/im.riot.Riot && rm -rf cache/* && rm -rf config/Element/GPUCache or for short in one shot for shells supporting it... rm -rf $HOME/.var/app/im.riot.Riot/{cache/*,config/Element/GPUCache} |
Upstream fix electron/electron#40467 |
Steps to reproduce
Outcome
What did you expect?
Expected regular element desktop screen to recover after restart
What happened instead?
I see only white screen.
If I start element from console in the log I see lots of messages like this:
When I try to get logs via /rangeshake command it does not work either
Operating system
Ubuntu 22.04 / 5.19.0-46-generic #47~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jun 21 15:35:31 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Application version
1.11.35
How did you install the app?
following guide on element insallation page via apt-get
Homeserver
matrix.org
Will you send logs?
No
The text was updated successfully, but these errors were encountered: