Bug 449140 - After change of scaling and plugging back in HDMI, screens are no longer touching, so pointer becomes confined to one of them
Summary: After change of scaling and plugging back in HDMI, screens are no longer touc...
Status: CONFIRMED
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.27.4
Platform: Neon Linux
: NOR major
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2022-01-25 13:13 UTC by postix
Modified: 2023-10-05 16:52 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
KWin support information: Step 1 (6.80 KB, text/plain)
2022-01-25 13:13 UTC, postix
Details
KWin support information: Step 3 (6.71 KB, text/plain)
2022-01-25 13:17 UTC, postix
Details
KWin support information: Step 5 (6.80 KB, text/plain)
2022-01-25 13:27 UTC, postix
Details
Screenshot: Step 5 (1.71 MB, image/jpeg)
2022-01-25 13:33 UTC, postix
Details

Note You need to log in before you can comment on or make changes to this bug.
Description postix 2022-01-25 13:13:38 UTC
Created attachment 145907 [details]
KWin support information: Step 1

STEPS TO REPRODUCE
1. 4k@200% DP monitor (primary, left) + FullHD@100% HDMI, adjacent to each other in KScreen
2. Changed scaling of DP to 100%
3. Unplugged the HDMI monitor
4. Changed scaling of DP to 200%
5. Plugged back in the HDMI monitor

OBSERVED RESULT
Logically the two monitors are now very far apart and all windows and the mouse are confined to the primary monitor, i.e. cannot be moved to the other screen

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon Testing
KDE Plasma Version: 5.23.90
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
Wayland
Comment 1 postix 2022-01-25 13:17:23 UTC
Created attachment 145908 [details]
KWin support information: Step 3
Comment 2 postix 2022-01-25 13:27:03 UTC
Created attachment 145909 [details]
KWin support information: Step 5
Comment 3 postix 2022-01-25 13:33:37 UTC
Created attachment 145911 [details]
Screenshot: Step 5
Comment 4 Nate Graham 2022-11-10 19:05:20 UTC
I can replicate this setup (with the screens' scale factors swapped, but that won't make a difference) and I can reproduce the issue with current git master.
Comment 5 postix 2023-04-10 15:42:07 UTC
Still reproducible with 5.27.4
Comment 6 Zamundaaa 2023-10-05 16:52:57 UTC
This problem is caused by the position of outputs being remembered separately from mode and scale. As a possible solution, we could maybe store the relationship between outputs in the output config, instead of only an absolute position