Bugzilla – Bug 1216216
Electron fails to render with “Skia shader compilation error” on Intel GPU
Last modified: 2023-10-26 08:17:41 UTC
Created attachment 870152 [details] Screenshot of a running signal-desktop application I get the following on openSUSE Tumbleweed since appr. snapshot 20231008 as seen in the attached screenshot. The same version from network:/im:/signal built for Leap 15.5 runs properly. tumbleweed# rpm -qa | egrep 'signal|nodejs' nodejs-electron-25.9.0-1.1.x86_64 signal-desktop-6.34.0-1.1.x86_64 signal-libringrtc-2.33.0-2.1.x86_64 leap-15.5# rpm -qa | egrep 'signal|nodejs' nodejs-electron-25.9.1-lp155.1.1.x86_64 signal-desktop-6.34.0-lp155.1.1.x86_64 signal-libringrtc-2.33.0-lp155.2.1.x86_64 I'll attach another file containing the logs shown in a terminal soon.
Created attachment 870153 [details] Logs from running signal-desktop in a screen session
What is your GPU? Do you have anything entered in `~/.config/electron-flags.conf`?
Also if you can run `electron chrome://gpu` please click “copy record to clipboard” and paste it here.
Created attachment 870158 [details] Output from running "electron chrome://gpu"
(In reply to dziobian from comment #2) > What is your GPU? Do you have anything entered in > `~/.config/electron-flags.conf`? File ~/.config/electron-flags.conf does not even exist. Here is some info about my GPU: $ inxi -G Graphics: Device-1: Intel RocketLake-S GT1 [UHD Graphics 750] driver: i915 v: kernel Display: x11 server: X.Org v: 21.1.8 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1920x1200~60Hz API: OpenGL v: 4.6 Mesa 23.2.1 renderer: Mesa Intel Graphics (RKL GT1)
Please try
Please try removing the directories ~/.config/Signal/DawnCache and ~/.config/Signal/GPUCache If that fixes the problem, then this is an issue known by Chromium upstream: https://bugs.chromium.org/p/chromium/issues/detail?id=1442633
(In reply to dziobian from comment #7) > Please try removing the directories > ~/.config/Signal/DawnCache and ~/.config/Signal/GPUCache > > If that fixes the problem, then this is an issue known by Chromium upstream: > https://bugs.chromium.org/p/chromium/issues/detail?id=1442633 Fixes is. Signal-desktop works again. Thank you!
duplicate of chromium bug *** This bug has been marked as a duplicate of bug 1214274 ***
Created attachment 870175 [details] Autostart file to empty existing cache directories and replace them with links to some directory below /tmp Indeed, the problem is fixed by this. As I am multi-booting between Leap 15.5 and Tumbleweed I have created a .config/autostart file to remove the two directories when logging in, and then create two temporary directories in /tmp as a target for the two (now) symbolic links .config/Signal/{DawnCache,GPUCache}. See this attachment.
Created attachment 870176 [details] Shared xdg autostart file for Signal desktop to move cache directories to where they belong to The more I think about this, I believe the two directories DawnCache and GPUCache don't belong into ~/.config/Signal but should be stored in ~/.cache/Signal. I changed my former autostart file into this new one which can be stored at /etc/xdg/autostart to implement the proper change for every user.