Bug 431533 - Windows get pushed to non-primary window
Summary: Windows get pushed to non-primary window
Status: RESOLVED DUPLICATE of bug 378896
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.20.2
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-13 10:25 UTC by jan.claussen10
Modified: 2021-08-19 19:36 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 jan.claussen10 2021-01-13 10:25:15 UTC
SUMMARY
This is super annoying. When I have an external screen connected and turn off my laptop screen everything is fine. Since I have a convertible laptop I sometimes activate the laptop screen as secondary screen to use it as a wacom tablet. When I do, all my windows are pushed to the laptop screen and I have to manually drag every single window back. 

STEPS TO REPRODUCE
1. Connect external screen and deactivate laptop screen
2. Re-activate laptop screen


OBSERVED RESULT
Windows get pushed to the secondary laptop screen

EXPECTED RESULT
The windows should stay on the primary screen

SOFTWARE/OS VERSIONS

Linux: Manjaro
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
I have an ThinkPad X380 Yoga, but don't think it is related
Comment 1 Nate Graham 2021-01-13 19:34:25 UTC
When you activate the laptop screen, is is marked as the primary or the secondary? And is it to the left or the right of the external screen?
Comment 2 jan.claussen10 2021-01-13 21:28:25 UTC
It is marked as the secondary one and is left from the external which is primary. All new programs also open on the secondary.
Comment 3 Nate Graham 2021-01-14 04:58:37 UTC
Ah yeah, that. :(

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

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