Summary: | Wayland - HiDPI screen scaling broken after login to the desktop | ||
---|---|---|---|
Product: | [Plasma] KScreen | Reporter: | Sławek <slawek> |
Component: | common | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | meven29, nate, xaver.hugl |
Priority: | HI | Keywords: | wayland |
Version: | 5.23.3 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Sławek
2021-11-18 08:53:57 UTC
I just hit this issue again after login into the desktop. Here is output of the kscreen-doctor when resolution was broken: kscreen-doctor -o Output: 1 unknown eDP-1-unknown disabled connected Panel Modes: 0:1920x1080@60*! Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic Output: 2 Goldstar Company Ltd LG HDR 4K/345575 enabled connected primary Unknown Modes: 0:3840x2160@30 1:2560x1440@60 2:1920x1080@60 3:1920x1080@60 4:1920x1080@60 5:1600x900@60 6:1280x1024@60 7:1280x800@60 8:1280x720@60 9:1280x720@60 10:1280x720@60 11:1024x768@60 12:800x600@60 13:720x480@60 14:720x480@60 15:640x480@60 16:640x480@60 17:640x480@60 18:3840x2160@60*! Geometry: 0,0 2560x1440 Scale: 1.5 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic primary Then I run kscreen-doctor to fix it: kscreen-doctor output.1.disable output.2.enable output.2.mode.3840x2160@60 output.2.scale.1.5 but it changed nothing. So I run: kscreen-doctor output.1.disable output.2.enable output.2.mode.1280x800@60 which changed resolution to 1280x800 and fixed desktop that whole (huge) desktop was displayed and mouse coursor was working properly. Then I again run kscreen-doctor output.1.disable output.2.enable output.2.mode.3840x2160@60 output.2.scale.1.5 And I have fixed my desktop finally :) I couldn't reproduce your issues using a 2560x1440* screen at 1.5 scale with plasma 5.24 (dev version). My ongoing patch https://invent.kde.org/plasma/kscreen/-/merge_requests/57 has a few fixes that should help your case. I was able to reproduce this in 5.23 as well, but it's fixed for me now in current git master. I think some code changes already fixed it. That MR also looks like it could help, for any remaining cases. Thx a lot. I will be then waiting for 5.24. Now with some simple script which uses kscreen-doctor it's easy for me to fix that resolution after log in to the desktop at least :) |