Bug 422073

Summary: Screen layout problem when switching between 2 sets of dual monitors of different resolutions
Product: [Plasma] KScreen Reporter: Mark Eaton <eaton.mark>
Component: commonAssignee: kscreen-bugs-null <kscreen-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate
Priority: NOR    
Version: 5.18.3   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Mark Eaton 2020-05-25 22:41:02 UTC
I run kde in a virtual machine on my work laptop and regularly switch between it having two monitors of 1900x1200 and two monitors of 2560x1440 (ie office/home). When changing between the two setups, the monitors are either overlapped or have a space between them and mouse clicks are not where the mouse appears to be. In addition when overlapped the area on display 1 which is covered by display 2 cannot receive mouse input. 
The option to save the display layout unfortunately doesn't work, possibly because they displays are virtual and it can't distinguish between the two different setups (always called Virtual1 and Virtual2).

STEPS TO REPRODUCE
1. Run KDE in a virtual machine with 2 monitors both of a resolution 1
2. Restart VM with 2 monitors of a resolution 2

OBSERVED RESULT
The two monitors are now either overlapped or have a space between them and the mouse location is not what is observed making it very difficult to fix the display setup.

EXPECTED RESULT
I would expect, that the displays never be partially overlapping as this doesn't make sense.
I would expect that the displays not have a space between them by default.
I would also expect the saved layouts to distinguish between two sets of monitors that have different resolutions even if they are both virtual displays. (possibly it needs to use the screen size as part of the identification)


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 19.10
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 
Qt Version: 5.12
Comment 1 Nate Graham 2022-11-08 19:10:11 UTC
See Bug 459744 and Bug 453926. Arbitrarily marking as a duplicate of Bug 453926 since we can't multi-dupe.

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