hyprwm
windowrulev2 = immediate,fullscreen:1 , kitty freeze
Regression?
No
System Info and Version
System/Version info
Hyprland, built from branch at commit 9a09eac79b85c846e3a865a9078a3f8ff65a9259 (props: bump version to 0.42.0).
Date: Wed Aug 7 19:17:10 2024
Tag: v0.42.0, commits: 5069
Description
kitty freeze in full screen when i enable tearing
How to reproduce
enable tearing and fullscreen kitty
Crash reports, logs, images, videos
No response
Why would you want to enable tearing for Kitty?
Probably to reduce input latency
Actually I can reproduce this. I cannot use immediate mode roughly since version 0.43 on any app as it will freeze as soon as the window gains solitarity. Doesn't matter if it's a wayland native or xwayland window.
Why would you want to enable tearing for Kitty?
i want to set tearing for any fullscreen application so my games have it , and i dont wan't other applications to be effcted or freezed
- i dont need tearing in my applications but i just want everything to work and not adding endless window roles for every game i run
You could do something like windowrulev2 = immediate, class:^(steam_app_.*)$.
This would enable tearing for all games running with proton.
@firashacker Which GPU do you run? Any chance that it is an NVIDIA card? Me and a frined cannot enable immediate mode anymore without getting freezes and we both run NVIDIA, but it works on an AMD system.
@firashacker Which GPU do you run? Any chance that it is an NVIDIA card? Me and a frined cannot enable immediate mode anymore without getting freezes and we both run NVIDIA, but it works on an AMD system.
i have radeon rx6600
You could do something like
windowrulev2 = immediate, class:^(steam_app_.*)$.This would enable tearing for all games running with proton.
this might be helpful but it doesn't apply for all the titles i play
Hello there!
This issue has been closed, as we are moving from issues to discussions. More about this can be found here and in #9854.
Firstly, please make sure this issue is still relevant in latest Hyprland. If so, we ask you to open a discussion (please read the discussion guidelines first, in the pinned post)
Thank you for your understanding!
Why isn't this just converted into a discussion? The issue is still relevant.
Because it was closed by a script that closed all 1300 open issues. If this issue is still relevant, reading the discussion guidelines and opening a new one takes 5 minutes.
Hmm - but now any new discussion for these 1300 issues will lack the previous context that already existed. I probably can't change your mind about this, but this feels like a strange decision regarding the discoverability and traceability of existing issues.