SUMMARY In the kscreens kcm one can arrange the positions of the screens. While it makes sense to put screens next to each other at some edge, putting them above another seems less useful, covers the screen below in the kcm and also causes visual glitches. I guess this needs to be "fixed" at two places: It should not be allowed to do configure some stacked screens by the user in the KScreen KCM _and_ it also should not happen automatically when plugging screens in and out. For instance, in Gnome placing a screen above another screen is not possible at all in the configuration. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE TW KDE Plasma Version: Plasma 5.25.5+ KDE Frameworks Version: 5.98 Qt Version: 5.15.5
*** This bug has been marked as a duplicate of bug 459253 ***
I'm sorry, but this is not a duplicate. This is about the possibility to move one screen on top of each other. If screens should be cloned respectively mirrored, this should probably be done in a better way in terms of the UI. If this the current approach of cloning, it has too many downsides in the UI: * The screen on top covers the screen below * Unintuitive * What does partly covering mean? * etc.
The bug report title is "KScreen allows to stack screens and sometimes after plugging screens in and out screens are stacked automatically causing visual glitches". "KScreen allows to stack screens" is a critique of the current design. "and sometimes after plugging screens in and out screens are stacked automatically causing visual glitches" is a bug. We can't have one bug report tracking two things, so I arbitrarily decided to make this bug report about the bug, which is a duplicate of Bug 459253. That's what happens when you use one but report to try to do two separate things. :) See https://community.kde.org/Get_Involved/Issue_Reporting#Multiple_issues_in_a_single_Bugzilla_ticket. To critique the current design that allows overlapping in the first place, please file a new bug report. And in the future try to avoid reporting multiple things in the same bug report. Thanks! *** This bug has been marked as a duplicate of bug 459253 ***
I actually reported only one bug, but I had forgot to adjust the misleading title, aw. I will report a new one with basically the same text but the first part of the title only...