Summary: | off-by-one pixel activating secondary monitor (hidpi) | ||
---|---|---|---|
Product: | [Plasma] KScreen | Reporter: | Thiago Macieira <thiago> |
Component: | common | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | ashark, kde, krzysiek, nate |
Priority: | NOR | ||
Version: | 5.19.2 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
URL: | https://www.youtube.com/watch?v=3HVmvYqYir8 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Thiago Macieira
2020-07-06 16:43:24 UTC
Same here - with two 2560x1440 displays (one 144Hz, other 60Hz, DPI forced to 96, global scale 100%), starting with the first screen enabled, second disabled, enabling the second display in KCM positions it at (0, 0) when the second, just added screen is held with the left mouse button. On Apply, it gets positoned to (2559, 0) and shares one line with the primary display, causing various odd issues. Repositioning the screen manually in KCM to (2560, 0) before hitting Apply fixes that just fine. I can reproduce this issue reliably every time. Software: - Arch Linux, kernel 5.10.7 - Plasma 5.20.5 - Frameworks 5.78.0 - Qt 5.15.2 I can confirm, this is still a case on KDE Neon 5.22.2 My screen profile from ~/.local/share/kscreen [ { "enabled": true, "id": "e26f74120a68171ca3762fbd7da4bdbf", "metadata": { "fullname": "xrandr-AU Optronics", "name": "eDP" }, "mode": { "refresh": 60.163848876953125, "size": { "height": 1080, "width": 1920 } }, "pos": { "x": 2560, "y": 1080 }, "primary": true, "rotation": 1, "scale": 1 }, { "enabled": true, "id": "5563920f01dcca21cd359eb077cb46d3", "metadata": { "fullname": "xrandr-LG Electronics-LG ULTRAWIDE-419722", "name": "DisplayPort-2" }, "mode": { "refresh": 59.978424072265625, "size": { "height": 1080, "width": 2560 } }, "pos": { "x": 0, "y": 0 }, "primary": false, "rotation": 1, "scale": 1 }, { "enabled": true, "id": "477765dc89cd85155bdd8db486371215", "metadata": { "fullname": "xrandr-Dell Inc.-DELL P2419H-FLW9BR2", "name": "DisplayPort-3" }, "mode": { "refresh": 60, "size": { "height": 1080, "width": 1920 } }, "pos": { "x": 2559, "y": 0 }, "primary": false, "rotation": 1, "scale": 1 }, { "enabled": true, "id": "dc6acfd333acebcd573153b1ecb7b3d8", "metadata": { "fullname": "xrandr-Iiyama North America-PL2474H-11669V9A09425", "name": "DisplayPort-4" }, "mode": { "refresh": 60, "size": { "height": 1080, "width": 1920 } }, "pos": { "x": 4480, "y": 0 }, "primary": false, "rotation": 1, "scale": 1 } ] I can confirm. On of side effects is that start menu is opened on wrong monitor. Lets assume your second monitor is to the right of first monitor. It is not obvious to user why this is happening, because it looks like all is ok, monitors are located correctly. But in reality the panel overlaps to the first monitor and so start menu button clicked on the second monitor opens menu in the first monitor (at location near the second monitor, not in the location of first monitor's start menu button). Another issue is that you cannot distinguish that situation in screen arrangement settings. And it is required two steps to fix. Let me explain in more details: 1) Be in situation when you are in off-by-one_pixel-state (for example, by plugging second monitor to the gpu). 2) Go to screen settings, drag the second monitor to some another position (for example slide it a bit vertically). 3) You will see that apply button is activated (do not press it yet). 4) Drag the second screen back where it was. 5) You will see that apply button is deactivated. You think that all is normal. But you are still in off-by-one_pixel situation (start menu opens at wrong monitor). Actually, to fix, you need to save configuration at step 3. Then at step 5 you will again see the active Apply button. And then after you press it, you fix the off-by-one_pixel state. Thank you for the bug report. Unfortunately we were not able to get to it yet. Can we ask you to please check if this is still an issue with Plasma 5.25 or 5.26? If it is, please add a comment with the output of `kscreen-doctor -o` and change the status to CONFIRMED. If not, or if you can't because you no longer use this setup, you can change the status to RESOLVED WORKSFORME. Thanks a lot! I *think* this was still an issue on 5.25, but I'm currently on 5.26 + NVIDIA 520.56.06 drivers, so I'm affected by another bug that forces me to temporarily use disman+kdisplay to be able to toggle any displays at all after the environment starts. I'll try to get you the data on just kscreen this weekend. *** This bug has been marked as a duplicate of bug 455394 *** Alright, finally had some time to retest this again, and it's still an issue on KDE 5.26.3. I've also tried applying https://invent.kde.org/plasma/kscreen/-/commit/fab815b0564ea08202b5bd3429f580c6c5a742d3 onto kscreen-5.26.3 from the linked bug and it's still no good. Output of kscreen-doctor -o after enabling the second display: Output: 66 DP-1 disabled disconnected DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 67 DP-2 disabled disconnected DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 68 HDMI-1 disabled disconnected HDMI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 69 DP-3 enabled connected primary DisplayPort Modes: 100:1440x480@60 101:832x624@75 102:800x600@72 103:800x600@75 104:800x600@60 105:800x600@56 106:720x576@50 107:640x480@75 108:640x480@73 109:640x480@67 110:640x480@60 111:640x480@60 112:720x400@70 74:2560x1440@60*! 75:2560x1440@144 76:2560x1440@120 77:2560x1440@100 78:1920x1080@120 79:1920x1080@100 80:1920x1080@120 81:1920x1080@60 82:1920x1080@60 83:1920x1080@50 84:1920x1080@60 85:1920x1080@60 86:1920x1080@50 87:1920x1080@60 88:1280x1024@7589:1280x1024@60 90:1440x900@60 91:1152x864@75 92:1280x720@60 93:1280x720@50 94:1280x720@60 95:1440x576@50 96:1024x768@75 97:1024x768@70 98:1024x768@60 99:1440x480@60 Geometry: 0,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown primary Output: 70 HDMI-2 disabled disconnected HDMI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 71 DP-4 enabled connected DisplayPort Modes: 101:832x624@75 102:800x600@72 103:800x600@75 104:800x600@60 105:800x600@56 106:720x576@50 107:640x480@75 108:640x480@73 109:640x480@67 110:640x480@60 111:640x480@60 112:720x400@70 113:2560x1440@60*!114:1280x1440@60 115:1680x1050@60 116:1280x960@60 117:720x480@60 118:720x480@60 82:1920x1080@60 83:1920x1080@50 84:1920x1080@60 85:1920x1080@60 86:1920x1080@50 87:1920x1080@60 88:1280x1024@75 89:1280x1024@60 90:1440x900@60 92:1280x720@60 93:1280x720@50 94:1280x720@60 96:1024x768@75 97:1024x768@70 98:1024x768@60 Geometry: 2559,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr:incapable RgbRange: unknown Output: 72 HDMI-3 disabled disconnected HDMI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown In that case your bug is something else, so please open a new bug report for it. Thanks! *** This bug has been marked as a duplicate of bug 455394 *** |