Skip to content
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

awesome in combination with compton prevents gsync from working #2444

Open
Fybe opened this issue Oct 17, 2018 · 5 comments
Open

awesome in combination with compton prevents gsync from working #2444

Fybe opened this issue Oct 17, 2018 · 5 comments
Labels

Comments

@Fybe
Copy link

Fybe commented Oct 17, 2018

If compton is running and I start a game in awesome GSync does not work (checked with the visual indicator of the proprietary driver).
If compton is not running and I start a game in awesome GSync works.
If compton is running (with the same configuration) and I start a game in openbox GSync work.

I start compton with --unredir-if-possible which disables composition for fullscreen windows.
I suspect awesome doesn't mark windows as fullscreen properly for compton to detect them.

Output of awesome --version:
awesome v4.2 (Human after all)
• Compiled against Lua 5.3.4 (running with Lua 5.3)
• D-Bus support: ✔
• execinfo support: ✔
• xcb-randr version: 1.5
• LGI version: 0.9.2

@psychon
Copy link
Member

psychon commented Oct 17, 2018

@Fybe Do you happen to be able to run awesome with --no-argb and see if that makes a difference?

CC @yshui thoughts? From a quick look at the code, unredirect-if-possible depends on win_is_solid "liking" the window and I guess awesome's frame window having depth 32 makes win_is_solid not like the whole window.

If that's the case, it might be possible to detect the case of "frame window of depth=32 has the same size as its only child with depth=24, so the window actually is solid", right?

@yshui
Copy link

yshui commented Oct 17, 2018

@psychon yea, this is also why I complained about the 32bit visual earlier too.

@Fybe
Copy link
Author

Fybe commented Oct 17, 2018

@psychon Yes, running awesome with --no-argb does make a difference.

@sirrus233
Copy link

Confirming that I see identical behavior (minus running a game in openbox, which I did not test) to the original poster.

@psychon
Copy link
Member

psychon commented May 10, 2019

#2764 is a duplicate of this that has some patches to AwesomeWM to get rid of the frame window for fullscreen windows. That makes this issue go away.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants