Created attachment 160799 [details] minimal example script SUMMARY A user of my Kwin script has a problem where the clientFullScreenSet signal is not being emitted on Wayland (but it does work on X11). To confirm this, he has been kind enough to run the minimal example script I'm attaching here, and indeed he did not get the expected result (as seen below). STEPS TO REPRODUCE 1. Install the provided minimal example script (kpackagetool5 --type=KWin/Script --install ./fullscreen-test.tar.gz) 2. Enable the script 3. Toggle fullscreen on a window 4. Observe the logs (journalctl -t kwin_wayland -g 'fullscreen-test') OBSERVED RESULT ...kwin_wayland[...]: qml: fullscreen-test: script started EXPECTED RESULT ...kwin_wayland[...]: qml: fullscreen-test: script started ...kwin_wayland[...]: qml: fullscreen-test: clientFullScreenSet SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Incidentally, I am also running Arch Linux and the same versions of all the software listed in this report, but I can't reproduce the issue. For me, the clientFullScreenSet signal is emitted on both X11 and Wayland.
I can confirm that I'm also facing the same problem on Wayland. Same Plasma and Frameworks versions as OP, and QT version 5.15.9. I'm running NixOS unstable.
It also seems that on this user's machine (but again not on mine) clients are missing the fullScreen property — it always has a falsy value (regardless of whether the window is full screen or not), but I don't know the exact value (likely undefined).
(In reply to Peter Fajdiga from comment #2) > It also seems that on this user's machine (but again not on mine) clients > are missing the fullScreen property — it always has a falsy value > (regardless of whether the window is full screen or not), but I don't know > the exact value (likely undefined). I apologize, but after some more testing, I can see that the `fullScreen` property is present. Please ignore my previous comment.