-
-
Notifications
You must be signed in to change notification settings - Fork 593
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
unredir-if-possible froze screen #160
Comments
Does the screen freeze happen immediately after you start compton? Also IIUC, this problem doesn't happen at all if you set |
Yep, all correct. |
Can you run compton with |
Here you go: compton.log Command line was:
|
@alaviss I added some debug prints to the |
Here's the log with |
Reduce code duplication, also handle_new_window handles damage of mapped windows properly. Fixes #160 Signed-off-by: Yuxuan Shui <[email protected]>
@alaviss Should be fixed in |
It used to be unmap when we receive its MapNotify, but now since we discard events received before we grab X server, that event it lost. But it turns out we can just unmap it when it's first created, no need to wait for the MapNotify. Partially fix #160 Signed-off-by: Yuxuan Shui <[email protected]>
Reduce code duplication, also handle_new_window handles damage of mapped windows properly. Fixes #160 Signed-off-by: Yuxuan Shui <[email protected]>
Platform
Gentoo amd64
GPU, drivers, and screen setup
Intel HD 5500 on
modesetting
driver, mesa 18.3.6Environment
i3-gaps
Compton version
compton --version
:v6-rc1-122-g72ede42
compton --diagnostics
:Compton configuration:
Steps of reproduction
compton
Expected behavior
Not freezing the screen
Current Behavior
Froze the screen
The text was updated successfully, but these errors were encountered: