Window compositing won't start at login and I have enabled the compositor on startup. I need to restart plasmashell in order to enable compositor. I use KDE Neon 5.7.0 ISO Reproducible: Always Steps to Reproduce: 1. Login 2. Compositor won't start until you restart plasmashell Actual Results: compositor won't start automatically Expected Results: compositor should be started automatically Logout then login again should fix it. But, should I re-login just to activate compositor? I have created script to restart plasmashell and make it as a startup autostart, but it won't help. #!/bin/bash killall plasmashell && kstart5 plasmashell but if I run it manually, it'll help.
Created attachment 100054 [details] Compositor setting that I am using.
please provide output of: qdbus org.kde.KWin /KWin supportInformation when the compositor is running and when not running.
I think I have similiar issue. Before plasma 5.7 there was like 50% chance that composition will be on after login. After composition it's always off.
Created attachment 100066 [details] qdbus org.kde.KWin /KWin supportInformation (on)
Created attachment 100067 [details] qdbus org.kde.KWin /KWin supportInformation )off)
given the upload time and order: I think Martin wants to see the information when compositing is not "enabled" (need to restart plasmashell points something entirely different) on login, so please confirm you did *not* cause this state by explicitly suspending the compositor, but it actually reflects the situation right after the login.
ftr, I bet on bug #364641
Created attachment 100070 [details] kwin state after login no translucency Ok I blew it. I admit. I'm sorry. Composition is always on but translucency (and contrast effect) is off after login on plasma panel, notification popups and krunner. Sometimes contrast effect works on krunner after login but never on plasma panel. After disabling contrast effect there is still no translucency on plasma panel after login. After restart kwin everything works I don't want to hijack this bugthread maybe my problem is unrelated to the author's.
Created attachment 100071 [details] kwin after --replace translucency on
No problem ;-) And no: I'm pretty sure your both just facing bug #364641 (explanation of the failure over there, it's in libplasma, though. KWin isn't the problem at all. It's a simple race on the availability check for the compositor)
Assuming duplicate of the well known and fixed issue of bug #364641. In case the later version does not fix it, please reopen. *** This bug has been marked as a duplicate of bug 364641 ***