|
Bugzilla – Full Text Bug Listing |
| Summary: | Electron Applications Blank | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Nathan Wolf <me> |
| Component: | Other | Assignee: | Callum Farmer <gmbr3> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | brunopitrus, dheidler, felix.niederwanger, me, sebix+novell.com |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Output of chromium with error messages | ||
|
Description
Nathan Wolf
2023-10-14 14:56:54 UTC
dup *** This bug has been marked as a duplicate of bug 1214274 *** This seems to be cause by Chromium not properly invalidating shader cache after Mesa updates. A workaround is to remove the cache:
rm -rf ~/.config/{Bitwarden,Signal}/{Dawn,GPU}Cache
Thank you but this worked for Signal but not Bitwarden. I still have to --disable-gpu to get Bitwarden to work. What does it print on the console when you run `bitwarden-desktop` from the terminal? Same issue arises with VS Codium and also there, `codium --disable-gpu` makes the application work again. We don't ship a “VS Codium”. (We ship Code with VSCodium patches but it is branded as “Code - OSS”). Please don't complain about bugs in third-party software on the bugzilla. This happens as both to 3rd party applications like slack as well as to applications using system node, like element-desktop. To workaround this issue, cache needs to be deleted (as a user): rm -r ~/.config/*/GPUCache As of Tumbleweed Snapshot 20231022 this has been resolved. I had this issue until at least with TW 20231108, now I finally removed the caches to recover a working state. So I can't confirm that the issue was fixed in 20231022 Created attachment 870990 [details] Output of chromium with error messages The issue re-appeared, with openSUSE Tumbleweed 20231122. This is the output of Chromium without GPU: $ chromium --disable-gpu > [32630:32630:1126/204302.091768:ERROR:policy_logger.cc(157)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(163) Cloud management controller initialization aborted as CBCM is not enabled. > (chromium:32630): Gtk-WARNING **: 20:43:02.435: Theme directory /apps of theme adwaita-xfce has no size field Very clean and everything works. Without disabling GPU, the output is very long. I attached it here as file. It is full of error messages like these: > Location of variable sk_FragColor conflicts with another variable. > [658:658:1126/204427.054084:ERROR:shared_context_state.cc(100)] Skia shader compilation error reproducible, so re-opening (couldn't do that in one step with uploading the file) Sebastian you're reporting a bug in chromium, not electron. Please open a new bug. Closing this as invalid as people seem to treat this issue as a coathanger for all chromium GPU bugs. (In reply to Bruno Pitrus from comment #12) > Sebastian you're reporting a bug in chromium, not electron. Please open a > new bug. Closing this as invalid as people seem to treat this issue as a > coathanger for all chromium GPU bugs. Thank you for the prompt answer. I want to add that the same issue happens for VS Code, it was just easier to retrieve the logs from Chromium. *** This bug has been marked as a duplicate of bug 1214274 *** |