-
Notifications
You must be signed in to change notification settings - Fork 174
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
GPU webview acceleration is broken on Wayland #10005
Comments
OS: Fedora 38 (Workstation Edition) For me it's the opposite. By default, GPU acceleration is disabled and I get heavy flickering e.g inside the Library tab, maybe not as serve as seen in your video. Scrolling is very choppy too. After enabling GPU acceleration those issues where gone. |
I too have this issue |
I have also had horrendous flickering on pages other than Library with GPU acceleration on. |
Getting flickering with acceleration on and NVIDIA 3060 mobile. |
I am also facing same issue |
Having the same issue with Nvidia RTX3070 Heavy flickering when going into the shop. Stabilizes after a short while. Keeps reappearing when hovering over url bar in steam. |
To add to this, Big Picture mode has once again has broken hardware acceleration on NVIDIA Wayland, RTX 3080, 535.113.01 or the 545 beta drivers. |
Distro: Arch Flickering rapidly. Happens every time without fail. Disabling HW acceleration in Web views "fixes" the issue. Runtime and Native both have this issue. |
Your system information
Please describe your issue in as much detail as possible:
Recently steam's webview has started displaying seizures on Wayland when GPU webview acceleration is enabled. Disabling GPU acceleration seems to solve the issue. This also does not happen on X11, whether GPU acceleration is on or off. This happens on both Steam stable and Steam beta.
Steps for reproducing this issue:
It won't happen 100% time but should happen fairly soon:
video demo:
https://github.com/ValveSoftware/steam-for-linux/assets/42720874/f4d09823-d2c7-45e8-8078-df154f5f86fb
The text was updated successfully, but these errors were encountered: