Created attachment 112980 [details] kwinrc How to reproduce 1) Disable "Background contrast" desktop effect 2) Connect or disconnect external monitor I reproduced this bug on two different machines, brand new Dell Latitude and 4 years old Samsung ATIV 5. On both of them installed KDE neon 5.12.5. If "Background contrast" desktop effect is enabled everything works just fine.
Created attachment 112981 [details] screenshot
The notification you screenshot shows that an application blocks compositing. You can disable this feature in the settings. It has nothing to do with the background contrast or multiple screens.
>> You can disable this feature in the settings? What feature? "Allow applications to block compositing"? I disabled it and on the next monitor connection it happened again.
Created attachment 112983 [details] disabled Allow applications to block compositing
And what application can block compositing? Can I find it somewhere in logs?
Similar bug here on KDE neon 5.17.2. Attaching a secondary screen disables compositing when "Background contrast" is disabled. After I enabled this effect, compositing is no longer disabled on secondary display status change.
@Piotr Is compositing blocked in your case too?
"Allow applications to block compositing" is enabled in my case.
Try to disable the feature and see if the problems happens again.
s/problems/problem/
I'm experiencing the same issue with kwin_x11 5.18.5. It persists even with "Allow applications to block compositing" switched off.
Happening to mine as well. Even with Background contrast enabled or Allow applications to block compositing is disabled everytime I attach a secondary display compositing is blocked I'm using an optimus laptop which is a Dell XPS 15 7590 and the Nvidia GPU enabled. Using Plasma 5.18.5 on Manjaro 20.0.2. This didn't happen I believe before 5.18 but not entirely sure.
Can confirm with "background contrast" disabled I also receive the same issue. Turning on or off "Allow applications to block compositing" has no affect. KDE: 5.19.2 KDE Framework: 5.71.0 QT: 5.15.0 Kernel: 5.7.6 GPU: Radeon RX570 with amdgpu
I have this bug too. Disabling „Let applications block compositing“ doesn’t change anything. I just started recently though. Like about one month ago.
@Rich Grundy: Are you on Manjaro too?
(In reply to jan.claussen10 from comment #15) > @Rich Grundy: Are you on Manjaro too? Arch standard, so kinda.
I'm on Manjaro with KDE 5.20.5 and experience the same. I also have this problem after my screen went to sleep. With enabled "Background contrast" desktop effect the problem is gone. I execute `kwin_x11 --replace &` each time after it happens to restore compositing. I'm using proprietary Nvidia drivers.
Same problem here. This is critical for everyday usage, it is a bit strange, that it has not been adressed as priority.
Created attachment 135209 [details] attachment-22042-0.html Yeah, hasn't been fixed for almost a year now..
Same problem connecting/disconnecting monitors with KDE plasma 5.21.3 (frameworks 5.80.0), Manjaro 21.0. But also encountered the issue with 5.20. Desktops effects get suspended and can easily be re-enabled with alt+shift+f12, but it is annoying. Enabling "background contrast" fixes the problem for some reason.
Still an issue 2 years later, this is super annoying to new users and usability I can tell you that much.
Can somebody try to reproduce the issue and post kwin's output? Please run kwin as follows env QT_LOGGING_RULES="kwin_scene_opengl.debug="true" kwin_x11 --replace
(In reply to Vlad Zahorodnii from comment #22) > Can somebody try to reproduce the issue and post kwin's output? Please run > kwin as follows > > env QT_LOGGING_RULES="kwin_scene_opengl.debug="true" kwin_x11 --replace I did this command but I can't find the logs.
Created attachment 139233 [details] kwin logs I am only able to reproduce this bug when booting connected with an external screen. (KDE neon 5.22) Here are the logs with journalctl with QT_LOGGING_RULES="kwin_*.debug=true" (line 79) kwin_scene_opengl: Suspending compositing because viewport limits are not met
I am suffering from the same problem. This bug should get far more attention!