Bug 418548 - Windows move to different displays when opening the laptop lid
Summary: Windows move to different displays when opening the laptop lid
Status: RESOLVED DUPLICATE of bug 296673
Alias: None
Product: kwin
Classification: Plasma
Component: core (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-06 15:10 UTC by Jens Reimann
Modified: 2020-09-12 03:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jens Reimann 2020-03-06 15:10:35 UTC
SUMMARY

Having a multi screen setup, with two screens on a docking station, attached to a laptop. I have the laptop lid closed most of the time. However, every now and then, I need to open the lid (e.g. for a video conferencing session).

What happens is that the windows move to different screens. It looks like that the new screen is inserted before all other screens, all windows move one screen left. Closing the lid reverts to the original order.

STEPS TO REPRODUCE
1. Have two active screens and some windows open.
2. Open laptop lid, new screen gets added
3. Bang

OBSERVED RESULT

It looks like windows consistently one screen to the left.

EXPECTED RESULT

I would expect the application windows to stay on their current screen. No matter if a new screen gets added/removed. This is the behavior on GNOME and Cinnamon.

SOFTWARE/OS VERSIONS
Windows: X
macOS: X
Linux/KDE Plasma: 5.5.7
(available in About System)
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.67.0
Qt Version: 5.13.2

ADDITIONAL INFORMATION

Operating System: Fedora 31
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.67.0
Qt Version: 5.13.2
Kernel Version: 5.5.7-200.fc31.x86_64
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-8665U CPU @ 1.90GHz
Memory: 31.1 GiB of RAM
Comment 1 n3wance 2020-09-12 03:52:34 UTC

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