SUMMARY It seems like KWin has issues with placing windows on a second screen. My setup uses X and two screens with identical resolution (1080p), one is the laptop's screen and the second is an external monitor, connected through a USB-C docking station and a DisplayPort to HDMI cable. It is on top of the laptop's screen, both physically and in the settings. When I connect the monitor, KWin correctly detects it and shows windows on it, but those windows appear to be placed incorrectly. As an example, the application launcher opens in the centre of the screen instead of the left corner where the related button is. Windows then appear not to be able to move around the laptop's screen correctly, as if there was an invisible border. Restarting KWin makes the issue go away. STEPS TO REPRODUCE 1. Connect an external screen. OBSERVED RESULT Windows and widgets are not placed correctly and behave weirdly. EXPECTED RESULT Windows and widgets work normally. SOFTWARE/OS VERSIONS Linux: KDE neon KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION
Created attachment 144575 [details] Latte Dock log I am moving this issue from KWin to Latte as I found out that the issue, which I initially thought was stemming from KWin, is actually from Latte Dock. Whenever I encounter the issue, quitting Latte makes things work as they should, which is quite a clear indication that the issue stems from Latte. I am attaching a log from Latte.
my guess is that this will be fixed with upcoming 0.10.5 from commit: https://invent.kde.org/plasma/latte-dock/-/commit/ca83433ce0a2bf67decb66bc9e0620830c9884a4
(In reply to Michail Vourlakos from comment #2) > my guess is that this will be fixed with upcoming 0.10.5 from commit: > https://invent.kde.org/plasma/latte-dock/-/commit/ > ca83433ce0a2bf67decb66bc9e0620830c9884a4 Thank you for your help, Michail! I will test this once it's out.
is it fixed with 0.10.5?
(In reply to Michail Vourlakos from comment #4) > is it fixed with 0.10.5? I was only able to test it today with version 10.6. It does indeed fix the issue, thanks!
*** Bug 433561 has been marked as a duplicate of this bug. ***