Bug 398690 - Window position after new monitor is added
Summary: Window position after new monitor is added
Status: RESOLVED DUPLICATE of bug 406312
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-multiscreen (show other bugs)
Version: 5.13.5
Platform: Manjaro Linux
: NOR normal
Target Milestone: 1.0
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-16 01:24 UTC by Andrei
Modified: 2019-04-08 08:29 UTC (History)
4 users (show)

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


Attachments
Configuration screen of the monitors (31.63 KB, image/png)
2018-09-16 01:24 UTC, Andrei
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrei 2018-09-16 01:24:09 UTC
Created attachment 114987 [details]
Configuration screen of the monitors

I use KDE on my laptop with a external monitor, I got my laptop screen as a primary screen.

Every time I attach the monitor to the laptop, the windows move to that new monitor instead of staying on the device screen.

The same behavior happens when I minimize the windows before attaching the monitor to the laptop, when I de-minimize the windows, they show up on the external monitor, even if I let the cursor on the primary screen or click on the  wallpaper to bring the focus to that screen.

It acts like the shell is choosing the last monitor in the list of available monitors instead of the first, or the primary one
Comment 1 natrius+kde 2019-04-07 19:51:31 UTC
I have the same problem with my computer. 2 monitors connected with DVI and one TV that is used just sometimes. The middle monitor is my primary and when i unplug the left TV or plug it in again, all windows get moved to another monitor. 

When a new monitor is connected nothing should change with the current windows, the new monitor should be added without change.
Comment 2 David Edmundson 2019-04-08 08:29:15 UTC
This isn't feasible.
Comment 3 David Edmundson 2019-04-08 08:29:29 UTC
*** This bug has been marked as a duplicate of bug 406312 ***