Created attachment 140971 [details] Screenshot SUMMARY I have a laptop with an internal 4k screen, and an external 4k monitor attached via USB-C. Both have the same 4k resolution configured, but the systemsettings module shows screen sizes and layout not in the way it's actually configured. Also, the pager applet shows screen sizes in another different way that doesn't match either the actual configuration nor what systemsettings shows. STEPS TO REPRODUCE 1. Open systemsettings 2. Attach screen OBSERVED RESULT External screen is placed correctly at 3840,0. Internal screen uses 4k resolution, but system settings shows it's using 1920x1080. The Pager shows the internal display as much wider than the external one. EXPECTED RESULT Display resolution and layout that systemsettings shows should match the actual configuration. Pager should show display layout matching the actual configuration. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION It's possible the pager issue is a separate bug, but since it's also related to the display layout it might come from the same source. I can open a separate bug report if needed.
Created attachment 140972 [details] Screenshot with laptop screen configuration Better screenshot that actually shows the laptop screen configuration
*** Bug 445757 has been marked as a duplicate of this bug. ***
*** Bug 442090 has been marked as a duplicate of this bug. ***
The description is quite confused, but there is an underlying bug which I assume is what the commenter is talking about. We have a behavioural difference between X and wayland. On wayland we store the scale per screen. We also want to show the logical size, not the resolution, so Output::logicalSize() returns resolution/scale. This is 100% completely correct. However, if you go back into X we have a mishmash. We don't support per-output scaling so the logicalSize should match the resolution, but because it's saved per output Output::logicalSize returns something that makes no sense and we get this gap. Ideally Output::logicalSize should check which platform it's under and not include the scale part when running on X, but it's not trivial to do that nicely.
Related: https://invent.kde.org/plasma/kscreen/-/merge_requests/26 Which sort of does it at the wrong layer, but I also can't think of anything better.
I sort of get the explanation, but wouldn't that then be the case for both the internal *and* the external screen? Both of them are 4k for me and both of them have a scale factor of 2, yet only one of them is showing as different in systemsettings.
Oh, I think I get it now. I did log into a wayland session a couple times before I got my external screen, but not since then. So if I understood the merge request correctly, the resolution preview is wrong for the internal screen because *that* one was used in a wayland session, but it's not wrong for the external screen because it wasn't used in a wayland session yet. I suppose that would make sense.
(In reply to Nate Graham from comment #2) > *** Bug 445757 has been marked as a duplicate of this bug. *** I'm not sure that bug 445757 is actually a duplicate. This bug seems to be about logical sizes being calculated wrong, while bug 445757 is about the confusing display of resolutions in the pager applet in principle - the physical resolution is not shown, so users see the logical size and think that it's the physical resolution and that their display is not used at its full capability.
A possibly relevant merge request was started @ https://invent.kde.org/plasma/kscreen/-/merge_requests/57
*** Bug 446178 has been marked as a duplicate of this bug. ***
Git commit 4d025b68022405ce889b563ed67646ccbfe4a658 by Méven Car. Committed on 01/12/2021 at 16:54. Pushed by meven into branch 'master'. Compute logicalSize taking into account current config M +1 -1 kcm/output_identifier.cpp M +15 -8 kcm/output_model.cpp M +2 -2 kded/output.cpp https://invent.kde.org/plasma/kscreen/commit/4d025b68022405ce889b563ed67646ccbfe4a658
I can confirm that the patch fixes the screen resolution reporting in systemsettings. However, the pager issue remains, so that looks like a different bug. Will file a new one for that separately.
*** Bug 446508 has been marked as a duplicate of this bug. ***
(In reply to Heinz Wiesinger from comment #12) > I can confirm that the patch fixes the screen resolution reporting in > systemsettings. However, the pager issue remains, so that looks like a > different bug. Will file a new one for that separately. Yes it is a plasma-destkop / plasma-workspace issue.