Created attachment 114570 [details] screenshot of systemsettings going outside the shell I have two monitors with the same resolution. Even under wayland this worked until latest point release of 5.13 (at least in archlinux packages). This works in X11 plasma session. Another funny complication is the fact that XWayland windows can't receive mouse clicks when moved "outside" the desktop. Native wayland applications don't seem to be affected from this.
Please include your Qt version
Also, does this happen when you restart plasmashell? If so can you run with QT_LOGGING_RULES=qt.*.debug=true plasmashell --replace > plasma_log and attatch that plasma_log file
Possibly related bug - https://bugs.kde.org/show_bug.cgi?id=397621
Created attachment 114573 [details] Plasma log of running a session with two monitors Qt is 5.11.1 KDE Frameworks is 5.49.0 Both latest from archlinux "stable" (i.e. non-testing) repos. Restarting the session (or the whole computer for that matter) doesn't solve it. The issue is always reproducable. `plasma_log` file after that command is empty. I've just executed given command. Didn't do anything apart from waiting the session getting initialized and waiting a few seconds. Tried to add `2>&1` at the end of the command in order to record at least the stdout. There's plenty of things in there, see it attached.
*** Bug 397621 has been marked as a duplicate of this bug. ***
This bug is still reproducible on my machine after updating plasma and frameworks. Operating System: Arch Linux KDE Plasma Version: 5.14.1 Qt Version: 5.11.2 KDE Frameworks Version: 5.51.0 Kernel Version: 4.18.14-arch1-1-ARCH OS Type: 64-bit
Please reopen if still an issue on Qt 5.12
> Please reopen if still an issue on Qt 5.12 Thanks, the bug is no longer reproducible. Not sure if it's because of Qt: Operating System: Arch Linux KDE Plasma Version: 5.14.5 Qt Version: 5.12.0 KDE Frameworks Version: 5.54.0 Kernel Version: 4.20.1-arch1-1-ARCH OS Type: 64-bit Should I close it or leave it as WAITINGFORINFO?
I did some output size setting changes in Qt for an unrelated issue, so it's quite plausible it's fixed. We can always reopen if needed