[KScreen] [Bug 469653] [Wayland] Primary monitor changes after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=469653 --- Comment #14 from rthe...@protonmail.com --- (In reply to Nate Graham from comment #13) > So with the old cable, it's still broken in the same way, or still broken > but in a different way, or it's fixed now? I didn't change cables, I just swapped where they connect on GPU ( Dell cable where the HP usually is and vice-versa). And the way I have it set now seem to have fixed it. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469653] [Wayland] Primary monitor changes after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=469653 --- Comment #13 from Nate Graham --- So with the old cable, it's still broken in the same way, or still broken but in a different way, or it's fixed now? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469653] [Wayland] Primary monitor changes after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=469653 --- Comment #12 from rthe...@protonmail.com --- Hi Nate, Sorry it took me so long, but I have some news. I swapped the DP cables between Dell and HP monitors, and after resume the primary monitor was set to the other one! kscreen-doctor after swapping cables: Output: 1 DP-2 enabled connected priority 2 DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@144* 2:1920x1200@60 3:1920x1080@60 4:1920x1080@60 5:1920x1080@50 6:1600x1200@60 7:1680x1050@60 8:1280x1024@75 9:1280x1024@60 10:1280x800@60 11:1152x864@75 12:1280x720@60 13:1280x720@60 14:1280x720@50 15:1024x768@75 16:1024x768@60 17:800x600@75 18:800x600@60 19:720x576@50 20:720x480@60 21:640x480@75 22:640x480@60 23:640x480@60 Geometry: 480,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Never RgbRange: unknown Output: 2 DP-3 enabled connected priority 1 DisplayPort Modes: 0:3440x1440@60! 1:3440x1440@165 2:3440x1440@144* 3:3440x1440@120 4:3440x1440@100 5:3440x1440@75 6:2560x1440@120 7:1920x1200@60 8:1920x1080@120 9:1920x1080@100 10:1920x1080@60 11:1920x1080@60 12:1680x1050@60 13:1600x900@60 14:1280x1024@60 15:1440x900@60 16:1280x800@60 17:1280x720@60 18:1280x720@60 19:1024x768@60 20:800x600@60 21:720x480@60 22:640x480@60 23:640x480@60 Geometry: 0,1440 3440x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Never RgbRange: unknown After resume from sleep: Output: 1 DP-2 enabled connected priority 1 DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@144* 2:1920x1200@60 3:1920x1080@60 4:1920x1080@60 5:1920x1080@50 6:1600x1200@60 7:1680x1050@60 8:1280x1024@75 9:1280x1024@60 10:1280x800@60 11:1152x864@75 12:1280x720@60 13:1280x720@60 14:1280x720@50 15:1024x768@75 16:1024x768@60 17:800x600@75 18:800x600@60 19:720x576@50 20:720x480@60 21:640x480@75 22:640x480@60 23:640x480@60 Geometry: 480,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Never RgbRange: unknown Output: 2 DP-3 enabled connected priority 2 DisplayPort Modes: 0:3440x1440@60! 1:3440x1440@165 2:3440x1440@144* 3:3440x1440@120 4:3440x1440@100 5:3440x1440@75 6:2560x1440@120 7:1920x1200@60 8:1920x1080@120 9:1920x1080@100 10:1920x1080@60 11:1920x1080@60 12:1680x1050@60 13:1600x900@60 14:1280x1024@60 15:1440x900@60 16:1280x800@60 17:1280x720@60 18:1280x720@60 19:1024x768@60 20:800x600@60 21:720x480@60 22:640x480@60 23:640x480@60 Geometry: 0,1440 3440x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Never RgbRange: unknown It seems like the priority swaps between those two. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469653] [Wayland] Primary monitor changes after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=469653 --- Comment #11 from Nate Graham --- If you bring back the old cable, does the issue come back? If so, it might truly be a hardware issue, similar to another bug report I saw recently that was ultimately solved with a new HDMI cable. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469653] [Wayland] Primary monitor changes after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=469653 --- Comment #10 from rthe...@protonmail.com --- Alright, an interesting development has occured. I've changed the layout of the monitors, because I replaced the monitor arm so my monitors are one above another. This seem to have fixed the issue with swapping primary monitor somehow. I've had it like this since last Saturday, and the plasma taskbar stays where it's supposed to. So. to anyone reading this: changing monitor layout or swapping DP cables seem to have helped. This is what the kscreen-doctor output looks like Output: 1 DP-2 enabled connected priority 1 DisplayPort Modes: 0:3440x1440@60! 1:3440x1440@165 2:3440x1440@144* 3:3440x1440@120 4:3440x1440@100 5:3440x1440@75 6:2560x1440@120 7:1920x1200@60 8:1920x1080@120 9:1920x1080@100 10:1920x1080@60 11:1920x1080@60 12:1680x1050@60 13:1600x900@60 14:1280x1024@60 15:1440x900@60 16:1280x800@60 17:1280x720@60 18:1280x720@60 19:1024x768@60 20:800x600@60 21:720x480@60 22:640x480@60 23:640x480@60 Geometry: 0,1440 3440x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Never RgbRange: unknown Output: 2 DP-3 enabled connected priority 2 DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@144* 2:1920x1200@60 3:1920x1080@60 4:1920x1080@60 5:1920x1080@50 6:1600x1200@60 7:1680x1050@60 8:1280x1024@75 9:1280x1024@60 10:1280x800@60 11:1152x864@75 12:1280x720@60 13:1280x720@60 14:1280x720@50 15:1024x768@75 16:1024x768@60 17:800x600@75 18:800x600@60 19:720x576@50 20:720x480@60 21:640x480@75 22:640x480@60 23:640x480@60 Geometry: 480,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Never RgbRange: unknown -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469653] [Wayland] Primary monitor changes after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=469653 --- Comment #9 from rthe...@protonmail.com --- (In reply to Nate Graham from comment #8) > Thanks. Nothing looks crazy to me in there. > > Seems similar to the issue reported in Bug 466342. Yup, the report seems to be the same as my case, except with sleep instead of hibernation. In both cases, it started t after upgrade to Plasma 5.27. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469653] [Wayland] Primary monitor changes after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=469653 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466342 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #8 from Nate Graham --- Thanks. Nothing looks crazy to me in there. Seems similar to the issue reported in Bug 466342. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469653] [Wayland] Primary monitor changes after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=469653 --- Comment #7 from rthe...@protonmail.com --- Just for completeness sake, here's the output of doctor before and I after change primary once the screens got flipped from resume: (~)$ kscreen-doctor -o Output: 1 DP-3 enabled connected priority 2 DisplayPort Modes: 0:3440x1440@60! 1:3440x1440@165 2:3440x1440@144* 3:3440x1440@120 4:3440x1440@100 5:3440x1440@75 6:2560x1440@120 7:1920x1200@60 8:1920x1080@120 9:1920x1080@100 10:1920x1080@60 11:1920x1080@60 12:1680x1050@60 13:1600x900@60 14:1280x1024@60 15:1440x900@60 16:1280x800@60 17:1280x720@60 18:1280x720@60 19:1024x768@60 20:800x600@60 21:720x480@60 22:640x480@60 23:640x480@60 Geometry: 0,641 3440x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Never RgbRange: unknown Output: 2 DP-2 enabled connected priority 1 DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@144* 2:1920x1200@60 3:1920x1080@60 4:1920x1080@60 5:1920x1080@50 6:1600x1200@60 7:1680x1050@60 8:1280x1024@75 9:1280x1024@60 10:1280x800@60 11:1152x864@75 12:1280x720@60 13:1280x720@60 14:1280x720@50 15:1024x768@75 16:1024x768@60 17:800x600@75 18:800x600@60 19:720x576@50 20:720x480@60 21:640x480@75 22:640x480@60 23:640x480@60 Geometry: 3440,0 1440x2560 Scale: 1 Rotation: 2 Overscan: 0 Vrr: Never RgbRange: unknown (~)$ kscreen-doctor output.DP-3.primary (~)$ kscreen-doctor -o Output: 1 DP-3 enabled connected priority 1 DisplayPort Modes: 0:3440x1440@60! 1:3440x1440@165 2:3440x1440@144* 3:3440x1440@120 4:3440x1440@100 5:3440x1440@75 6:2560x1440@120 7:1920x1200@60 8:1920x1080@120 9:1920x1080@100 10:1920x1080@60 11:1920x1080@60 12:1680x1050@60 13:1600x900@60 14:1280x1024@60 15:1440x900@60 16:1280x800@60 17:1280x720@60 18:1280x720@60 19:1024x768@60 20:800x600@60 21:720x480@60 22:640x480@60 23:640x480@60 Geometry: 0,641 3440x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Never RgbRange: unknown Output: 2 DP-2 enabled connected priority 2 DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@144* 2:1920x1200@60 3:1920x1080@60 4:1920x1080@60 5:1920x1080@50 6:1600x1200@60 7:1680x1050@60 8:1280x1024@75 9:1280x1024@60 10:1280x800@60 11:1152x864@75 12:1280x720@60 13:1280x720@60 14:1280x720@50 15:1024x768@75 16:1024x768@60 17:800x600@75 18:800x600@60 19:720x576@50 20:720x480@60 21:640x480@75 22:640x480@60 23:640x480@60 Geometry: 3440,0 1440x2560 Scale: 1 Rotation: 2 Overscan: 0 Vrr: Never RgbRange: unknown -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469653] [Wayland] Primary monitor changes after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=469653 --- Comment #6 from rthe...@protonmail.com --- Sure Nate, Here you go: (~)$ kscreen-console bug xrandr --verbose== Screen 0: minimum 16 x 16, current 4880 x 2560, maximum 32767 x 32767 XWAYLAND1 connected 3440x1440+0+641 (0x41) normal (normal left inverted right x axis y axis) 800mm x 340mm Identifier: 0x23 Timestamp: 87292 Subpixel: unknown Gamma: 1.0:1.0:1.0 Brightness: 0.0 Clones: CRTC: 1 CRTCs: 1 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: RANDR Emulation: 1 non-desktop: 0 supported: 0, 1 3440x1440 (0x41) 1086.750MHz -HSync +VSync *current +preferred h: width 3440 start 3744 end 4128 total 4816 skew0 clock 225.65KHz v: height 1440 start 1443 end 1453 total 1568 clock 143.91Hz 1920x1440 (0x42) 606.500MHz -HSync +VSync h: width 1920 start 2096 end 2304 total 2688 skew0 clock 225.63KHz v: height 1440 start 1443 end 1447 total 1568 clock 143.90Hz 1600x1200 (0x43) 418.250MHz -HSync +VSync h: width 1600 start 1736 end 1912 total 2224 skew0 clock 188.06KHz v: height 1200 start 1203 end 1207 total 1307 clock 143.89Hz 1440x1080 (0x28) 338.500MHz -HSync +VSync h: width 1440 start 1568 end 1720 total 2000 skew0 clock 169.25KHz v: height 1080 start 1083 end 1087 total 1177 clock 143.80Hz 1400x1050 (0x44) 320.000MHz -HSync +VSync h: width 1400 start 1520 end 1672 total 1944 skew0 clock 164.61KHz v: height 1050 start 1053 end 1057 total 1144 clock 143.89Hz 1280x1024 (0x2a) 285.000MHz -HSync +VSync h: width 1280 start 1392 end 1528 total 1776 skew0 clock 160.47KHz v: height 1024 start 1027 end 1034 total 1116 clock 143.79Hz 1280x960 (0x2b) 267.250MHz -HSync +VSync h: width 1280 start 1392 end 1528 total 1776 skew0 clock 150.48KHz v: height 960 start 963 end 967 total 1046 clock 143.86Hz 1152x864 (0x45) 214.750MHz -HSync +VSync h: width 1152 start 1248 end 1368 total 1584 skew0 clock 135.57KHz v: height 864 start 867 end 871 total 942 clock 143.92Hz 1024x768 (0x46) 169.750MHz -HSync +VSync h: width 1024 start 1112 end 1216 total 1408 skew0 clock 120.56KHz v: height 768 start 771 end 775 total 838 clock 143.87Hz 800x600 (0x2e) 102.500MHz -HSync +VSync h: width 800 start 864 end 944 total 1088 skew0 clock 94.21KHz v: height 600 start 603 end 607 total 655 clock 143.83Hz 640x480 (0x47) 65.250MHz -HSync +VSync h: width 640 start 688 end 752 total 864 skew0 clock 75.52KHz v: height 480 start 483 end 487 total 525 clock 143.85Hz 320x240 (0x30) 15.000MHz -HSync +VSync h: width 320 start 336 end 360 total 400 skew0 clock 37.50KHz v: height 240 start 243 end 247 total 264 clock 142.05Hz 1920x1200 (0x48) 502.500MHz -HSync +VSync h: width 1920 start 2088 end 2296 total 2672 skew0 clock 188.06KHz v: height 1200 start 1203 end 1209 total 1307 clock 143.89Hz 1680x1050 (0x49) 384.500MHz -HSync +VSync h: width 1680 start 1824 end 2008 total 2336 skew0 clock 164.60KHz v: height 1050 start 1053 end 1059 total 1144 clock 143.88Hz 1440x900 (0x4a) 280.000MHz -HSync +VSync h: width 1440 start 1560 end 1712 total 1984 skew0 clock 141.13KHz v: height 900 start 903 end 909 total 981 clock 143.86Hz 1280x800 (0x4b) 221.000MHz -HSync +VSync h: width 1280 start 1384 end 1520 total 1760 skew0 clock 125.57KHz v: height 800 start 803 end 809 total 873 clock 143.84Hz 720x480 (0x4c) 72.500MHz -HSync +VSync h: width 720 start 768 end 840 total 960 skew0 clock 75.52KHz v: height 480 start 483 end 493 total 525 clock 143.85Hz 640x400 (0x36) 53.250MHz -HSync +VSync h: width 640 start 680 end 744 total 848 skew0 clock 62.79KHz v: height 400 start 403 end 409 total 438 clock 143.37Hz 320x200 (0x37) 12.500MHz -HSync +VSync h: width 320 start 336 end 360 total 400 skew0 clock 31.25KHz v: height 200 start 203 end 209 total 221 clock 141.40Hz 2560x1440 (0x4d) 808.750MHz -HSync +VSync h: width 2560 start 2792 end 3072 total 3584 skew0 clock 225.66KHz v: height 1440 start 1443 end 1448 total 1568 clock 143.91Hz 2048x1152 (0x4e) 514.250MHz -HSync +VSync h: width 2048 start 2224 end 2448 total 2848
[KScreen] [Bug 469653] [Wayland] Primary monitor changes after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=469653 --- Comment #5 from Nate Graham --- So it looks like which screen counts as output 1 and which counts as output 2 are getting switched around. Can you also attach the output of `kscreen-console bug`? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469653] [Wayland] Primary monitor changes after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=469653 --- Comment #4 from rthe...@protonmail.com --- Managed to get it flipped after second resume from sleep. Attaching also kscreen-doctor output (~)$ kscreen-doctor -o Output: 1 DP-3 enabled connected priority 2 DisplayPort Modes: 0:3440x1440@60! 1:3440x1440@165 2:3440x1440@144* 3:3440x1440@120 4:3440x1440@100 5:3440x1440@75 6:2560x1440@120 7:1920x1200@60 8:1920x1080@120 9:1920x1080@100 10:1920x1080@60 11:1920x1080@60 12:1680x1050@60 13:1600x900@60 14:1280x1024@60 15:1440x900@60 16:1280x800@60 17:1280x720@60 18:1280x720@60 19:1024x768@60 20:800x600@60 21:720x480@60 22:640x480@60 23:640x480@60 Geometry: 0,641 3440x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Never RgbRange: unknown Output: 2 DP-2 enabled connected priority 1 DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@144* 2:1920x1200@60 3:1920x1080@60 4:1920x1080@60 5:1920x1080@50 6:1600x1200@60 7:1680x1050@60 8:1280x1024@75 9:1280x1024@60 10:1280x800@60 11:1152x864@75 12:1280x720@60 13:1280x720@60 14:1280x720@50 15:1024x768@75 16:1024x768@60 17:800x600@75 18:800x600@60 19:720x576@50 20:720x480@60 21:640x480@75 22:640x480@60 23:640x480@60 Geometry: 3440,0 1440x2560 Scale: 1 Rotation: 2 Overscan: 0 Vrr: Never RgbRange: unknown -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469653] [Wayland] Primary monitor changes after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=469653 --- Comment #3 from rthe...@protonmail.com --- Created attachment 159019 --> https://bugs.kde.org/attachment.cgi?id=159019=edit Monitor layout after resume from sleep -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469653] [Wayland] Primary monitor changes after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=469653 --- Comment #2 from rthe...@protonmail.com --- Hi Nate, Yes, the output I provided from both the screenshot and kscreen-doctor is how it's supposed to be. I will paste here the output of both when the screens are 'flipped' after resume. Regards -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469653] [Wayland] Primary monitor changes after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=469653 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- According to the screenshot, the HP monitor is the primary one. And the output of kscreen-doctor -o also shows that DP-3 (which appears to be the widescreen HP monitor by resolution inspection) is listed as priority 1, which is correct. So from KScreen's perspective, everything is okay and it would seem that Plasma is at fault. Or did you take the screenshot and paste the kscreen-doctor -o output after you manually fixed things by running `kscreen-doctor output.DP-3.primary`? -- You are receiving this mail because: You are watching all bug changes.
