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
Wayland rendering backend not working #159
Comments
I guess you're using Flatpaks – and why I can't blame you for that, you should know that WebCord's Flathub repository is entirely maintained by the community. See #116.
Actually,
Have you tried turning on GPU optimizations in settings to test if that will help with at least few performance issues?
I'm not sure, but it could be because of Wayland not being passed to WebCord by Flatpak: You should try to open the issue at WebCord's Flathub repository in that case. |
Can confirm manually enabling wayland permission (using Flatseal) make it work. But for some reason it did not automatically use wayland platform (i already manually set EDIT: Ah looks like the flags is actually required for proper wayland support, sorry |
That's due to Electron/Chromium. They're quite unstable on Wayland, so it's only optional. |
In addition to this, I've tried to inject the |
Using the rpm installation I get a different experience then reported above. WebCord does launch using
Blue squares were added to remove some personal information however you can see the difference between the two despite both being maximized. I am using Fedora 36 and WebCord 3.5.0. |
Can confirm on WebCord flatpak. |
Likely related to electron/electron#34820. |
I believe most of the issues I was seeing will be fixed in electron/electron#34955 |
Great find! Althrough the original issue was because of Flatpaks, I may leave this open to track this pull request. |
Install flatpak version |
The PR has been recently merged into upstream and is present in Electron I guess I will close this issue and mark it as resolved. The issue will be resolved on the next release (since it will automatically bump Electron to the latest supported version). |
All the issues I observed previously are fixed in 3.8.1; Wayland is working great for me now!
|
@fontivan The last two shouldn't be required through, WebCord should apply these automatically. |
Aknowledgements
I have checked that there's no other issue describing the same or
similar problem that I currently have, regardless if it has been
closed or open.
I can confirm that this is not an issue with the Discord website,
but it is a problem specific to the WebCord itself.
I have tried running the build from the
master
branch and it doesnot have any fixes implemented according to my 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
(please write it in Additional context section).
Operating System / Platform
🐧️ Linux
Operating system architecture
x64 (64-bit Intel/AMD)
Electron version
19.0.6
Application version
v3.3.0
Bug description
Summary
Electron has massive input lag for text fields under Wayland, at least if an Nvidia GPU is being used. Chrome's/Electron's new
Ozone Wayland rendering backend can't be enabled
Details:
Electron works a lot better, when using the native Ozone Wayland rendering backend, which can be enabled with the flags
--enable-features=UseOzonePlatform --ozone-platform=wayland
.I have successfully applied this workaround to a bunch of different Electron apps (e.g. Element, Visual Studio Code...), however, when trying to do the same for Webcord, the application crashes with a segfault:
Does this maybe require a compile flag to be enabled?
Additional context
My System:
OS: Fedora 36
GPU: Nvidia RTX 3080
graphics driver: proprietary nvidia driver, version 510
Desktop Environment: Gnome 42.2
The text was updated successfully, but these errors were encountered: