Bug 456368

Summary:	Restoring a maximized window after disconnecting a screen places the window outside of the current screen
Product:	[Plasma] kwin	Reporter:	andrewchin873
Component:	multi-screen	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	nate, nerumo, plasma-bugs
Priority:	NOR	Keywords:	multiscreen
Version First Reported In:	5.25.2
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description andrewchin873 2022-07-05 20:50:29 UTC

SUMMARY
I have an external monitor as my main screen, placed to the left of my laptop screen. If I have a maximized application on the external monitor, disconnect the external monitor, then restore the application window on my laptop screen, the window moves itself to the right of my laptop screen (where my external monitor used to be). Desired behaviour is for the window to restore within the borders of my laptop screen. I only use Wayland, haven't tried X11's behaviour.


STEPS TO REPRODUCE
1. Maximize an application on a display/screen
2. Disconnect that display/screen and wait for the application window to automatically relocate to a connected screen
3. Unmaximize/restore the window

OBSERVED RESULT
Window moves itself to where the display/screen used to reside (but doesn't anymore since it's disconnected)

EXPECTED RESULT
Window unmaximizes/restores to a position within the current connected display/screen.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.18.6-1-default (64-bit)
(available in About System)
KDE Plasma Version: 5.25.2
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5

ADDITIONAL INFORMATION
Graphics Platform: Wayland

Comment 1 Marco Schmidlin 2025-05-28 06:45:03 UTC

I use Plasma 6.4 and this problem got worse, meaning that even more windows are lost to the disconnected external display :) . Even if I use the manual move command from the context menu, the window doesn't appear anymore.

Comment 2 Nate Graham 2025-05-28 16:02:39 UTC


*** This bug has been marked as a duplicate of bug 479694 ***