Bug 434970 - Windows are re arranged to primary monitor after unlock
Summary: Windows are re arranged to primary monitor after unlock
Status: RESOLVED DUPLICATE of bug 378896
Alias: None
Product: kwin
Classification: Plasma
Component: multi-screen (show other bugs)
Version: 5.20.5
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-26 13:21 UTC by Marco Ambu
Modified: 2021-08-19 19:36 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Ambu 2021-03-26 13:21:43 UTC
SUMMARY
When using multiple monitors, after unlocking after the energy saving timeout all the open windows are moved to the primary monitor even if they were in the secondary before the lock.

STEPS TO REPRODUCE
1. wait for the monitors to go off
2. press a key to show the unlock screen and type password

OBSERVED RESULT
When the session is back all the windows re-arranged in the primary monitor.
Also, applications in full screen in both monitors cannot see the second monitor again.

EXPECTED RESULT
When the session is back all the windows are where they were before locking (including the secondary monitor).

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Debian bullseye 5.10.0-5-amd64
(available in About System)
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.12.2

ADDITIONAL INFORMATION
This does not happen if I use Win+L to lock and then unlock before the monitor power saving timeout kicks in.
Comment 1 Nate Graham 2021-03-31 15:49:34 UTC
If your primary monitor by any chance not the left-most one?
Comment 2 Marco Ambu 2021-03-31 15:55:47 UTC
You are right: I have 2 monitors: my primary is on the right and the secondary is on the left.
That because I have an all-in-one so I cannot really change the primary I believe.
Comment 3 Nate Graham 2021-03-31 16:02:00 UTC
Yup, I thought so. It's an annoying known issue.

*** This bug has been marked as a duplicate of bug 427875 ***
Comment 4 Nate Graham 2021-08-19 19:36:44 UTC

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