Stuck on full gray screen on Kubuntu

[Spamakin]

Aknowledgements

• [X] I have checked that there is no other issue describing the same or similar problem that I currently have, regardless if it has been closed or open.

• [ ] This bug affects Discord website.

• [ ] This issue is confirmed to be reproduceable when WebCord is packaged on at least all three latest supported Electron major releases.

• [ ] This issue is reproduceable in Chrome, Chromium or any Chromium-based browser, e.g Brave or Edge (please write in Additional Context which browser you have used if it is neither Chrome nor unmodified Chromium).

• [ ] There are no fixes done to master which resolves this issue.

• [ ] My issue describes one of the unstable and/or not fully implemented features.

• [ ] I have found a workaround to mitigate or temporarily fix this issue in affected releases (please write it in Additional context section below).

Operating System / Platform

🐧️ Linux

Operating system architecture

x64 (64-bit Intel/AMD)

Electron version

N/A

Application version

WebCord v4.3.0, stable build

Bug description

If I open webcord, all I can see is this. This is also why I cannot display the Electron version or Application version. I have tried to reinstall, no luck. This does not occur on the web version or the official Linux client for Discord.

Additional context

No response

[SpacingBat3]

Electron version

N/A

Application version

N/A

Please fill these fields (see about window, webcord --version in CLI or version reported by package manager). I believe I've seen this bug before (when using custom CSS), but this was the case for older WebCord versions.

[SpacingBat3]

Also, is app running in Wayland enviroment (I suppose KDE might run both as X11 and Wayland sessions)?

[Spamakin]

Please fill these fields (see about window, webcord --version in CLI or version reported by package manager).

I cannot access the about window at all (that screenshot I've sent is as far as it gets) but I added the version (4.3.0 Stable Build).

Also, is app running in Wayland enviroment (I suppose KDE might run both as X11 and Wayland sessions)?

I think it's Wayland from googling around but I'm not 100% sure how to check this.

[fenndev]

Running Webcord 4.3.0 stable on Fedora 38, I'm also experiencing the same issue. I am running it on Wayland and using the .rpm from the Releases page here on Github.

Running the webcord --version command does not show an Electron version, but the version of Electron installed on my device (via electron --version) is v25.3.1. Here is a video of the steps to reproduce:

Screencast from 2023-07-24 15-39-15.webm

[SpacingBat3]

@Spamakin @fenndev Try running WebCord with --no-sandbox, some kernels (e.g. archlinux-hardened) don't support capabilities needed for Electron sandboxing in some cases. You might also try running older version of WebCord to check if this bug is a regression (most likely on Electron side) or rebuild WebCord on downgraded version of Electron.

[fenndev]

@SpacingBat3 I tried the following:

1. Tried --no-sandbox, did not resolve the issue
2. Reinstalled v4.3.0 - both the RPM and AppImage had this issue
3. Installed Webcord v4.2.0 and this resolved the issue, now working as expected

[Spamakin]

Similar story here: 1: Tried --no-sandbox, did not resolve issue, just a ton of errors + same issues as in screenshot 2: Reinstalled 4.3.0 amd64.deb, did not resolve issue 3: Installed 4.2.0 amd64.deb, resolved issue.

[r2rX]

It seems there might be a shader cache related issue with chromium and recent Mesa drivers...thus the GPU cache needs to be cleared. Head to $HOME/.config/WebCord/GPUCache/, delete the files present and then relaunch Webcord.

[Spamakin]

Ooooo yes this worked. Happily running version 4.3.0 now

[dpanter]

Deleting GPUCache files also sorted this for me, using Debian KDE Wayland, AMD GPU with Mesa-git. Webcord would sometimes show grey or corrupted window when running as native Wayland application, and eventually also break as XWayland application. Disabling WebGL and GPU optimization did nothing, but clearing cache fixed both.

[r2rX]

Are there any NVIDIA users that have encountered this issue (either in X11 or Wayland)?

[ZenitH-AT]

Yeah, Fedora 38 with an old GTX 750 Ti using X11. I tried deleting the GPU cache folder but it doesn't help. @r2rX

[r2rX]

Thanks for testing @ZenitH-AT . Interesting.....quite confounding.

[quazar-omega]

@ZenitH-AT Same here

OS	Fedora 38 Kinoite
Windowing system	Wayland
GPU vendor	Intel

[egerlach]

I'm also running into this. Deleting the GPUCache worked for a minute, but then it went gray again.

Distribution method: Flatpak OS: Debian 12 Windowing System: Xorg GPU vendor: AMD

I installed 4.3.0 from nixpkgs and it works... for now. I'll report back if that changes.

[SpacingBat3]

I believe the reports on v4.4.0 are of different cause (#452), therefore this issue will be closed as I'll make an assumption it was specific to Electron 25 and with v4.4.0 I bumped Electron version to 26. I suppose as @r2rX this was indeed due to conflict with GPUCache.

Also @fenndev's video clearly shows renderer is still running and this is purely graphical / window drawing issue. So this has nothing to do with #452 where according to the community, a renderer process crash occurs.

Take a note I didn't reproduce both of these issues, so both of these are somewhat setup-specific. Moreover this issue ticket was repored to be fixed by deleting GPUCache.

So yeah, please do not report there anything on newer WebCord, #452 already describes this problem. Also please avoid posting anything unhelpful for this issue, even logs that are not quite the same aren't really helping me or anyone in any way (since those errors are usually caused by different Chromium component and most likely aren't critical). I'll hide comments like these, hopefully to improve the focus on more helpful comments.