Bug 412428 - Automatic "Allow Applications to Block Compositing" seems to not be working
Summary: Automatic "Allow Applications to Block Compositing" seems to not be working
Status: RESOLVED DUPLICATE of bug 412353
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.16.90
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-28 20:33 UTC by Joe
Modified: 2019-09-28 20:38 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joe 2019-09-28 20:33:53 UTC
I noticed after upgrading to 5.16.90 that automatic suspension of compositing doesn't appear to be working for me anymore. I was going back to some more freesync testing, and noticed it wasn't turning on in any game. This included native games (Talos, SS3, etc), Feral Ports, and Proton games. I know at least the native/Feral games used to send the flag to turn it off automatically, which I thought was actually done at the SDL level. I have the settings "Allow Applications to Block Compositing" ticked off in System Settings. I am not sure when this actually broke (or if it is supposed to still work).

Steps to reproduce:

1. Open Steam
2. Launch any game in full screen
3. Notice that compositing isn't disabled (and things like Freesync are blocked)

Reproducible:

Always for me.

Work around:

1) Press  "shift" + "alt" + "f12"
2) Compositor turns off, things like Freesync immediately start working.


Operating System: Arch Linux (kde-unstable enabled, testing disabled)
KDE Plasma Version: 5.16.90
KDE Frameworks Version: 5.62.0
Qt Version: 5.13.1
Kernel Version: 5.3.1-arch1-1-ARCH
OS Type: 64-bit
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 15.6 GiB of RAM
GPU: NVIDIA  GTX 1070
Driver: 435.21
Comment 1 Vlad Zahorodnii 2019-09-28 20:38:31 UTC
*** This bug has been marked as a duplicate of bug 412353 ***