SUMMARY Have 3 monitors. All same model, resolution (1440p, 165hz) size etc... I keep my monitor on the right in portrait due to workspace constraints. Every time I reboot my right monitor goes back into landscape mode and I have to go into display settings and set it back. Very annoying. STEPS TO REPRODUCE 1. Log in with Wayland Session 2. Set monitor to portrait in display settings. 3. Reboot and log back on. OBSERVED RESULT Monitor set in portrait mode does not stay in portrait mode on reboot. EXPECTED RESULT I expect it to keep all my monitor layout positions on reboot. SOFTWARE/OS VERSIONS Latest Manjaro KDE Plasma KDE Plasma Version: 5.24.4 ADDITIONAL INFORMATION My hardware is all: AMD Motherboard - Gigabyte x570 AORUS Master, RAM - 32GB of Corsair Dominator Plus (3200mhz, 4x8gb CL15). CPU - 5800x, GPU - RX 6700xt
I believe this is supposed to be fixed in Plasma 5.25. Any chance you could use git master/"kde unstable" packages to test the fix and see if it works for you?
(In reply to Nate Graham from comment #1) > I believe this is supposed to be fixed in Plasma 5.25. Any chance you could > use git master/"kde unstable" packages to test the fix and see if it works > for you? I'm not sure exactly on how to go about doing this (sorry bit of a noob). I'm already on the unstable branch for packages (https://wiki.manjaro.org/index.php/Switching_Branches) which is how I'm on the latest 5.24.4 plasma version but that didn't fix the issue obviously. Do I need to go to command line or can this be grabbed from Discover - gui software center via AUR or official repo?
Don't worry about it. :) We'll call it fixed for now, and you can feel free to re-open it if you upgrade to 5.25 and discover that it's still broken for you.
(In reply to Nate Graham from comment #3) > Don't worry about it. :) We'll call it fixed for now, and you can feel free > to re-open it if you upgrade to 5.25 and discover that it's still broken for > you. This still doesn't work. I re-opened. I got latest 5.24.5 and that didn't fix the problem so really wanting to fix it I compiled my own KDE Plasma Desktop using the following instructions which resulted in me being able to run my compiled version and it saying KDE Plasma Version 5.25.80 and 5.94.0 KDE Frameworks Version in the "About this System" in System Settings. So not sure if I have to get something more latest? https://community.kde.org/Get_Involved/development
Darn. Thanks for checking!
(In reply to Nate Graham from comment #5) > Darn. Thanks for checking! Let me know what I can do to help :)
bug confirmed on X11 too. monitor set to portrait *system settings -> display configuration -> orientation) reverts back to landscape after reboot. plasma 5.25.4 KDE Frameworks 5.97.0 Qt 5.15.5
(In reply to kde from comment #7) > bug confirmed on X11 too. > monitor set to portrait *system settings -> display configuration -> > orientation) reverts back to landscape after reboot. > > plasma 5.25.4 > KDE Frameworks 5.97.0 > Qt 5.15.5 That's to bad it's still a problem. I got tired of waiting/checking every new plasma release for a fix that I am now on Gnome Wayland which works perfect.
Works fine here. Can someone affected rename or move (not delete!) their ~/.local/share/kscreen folder and try again?
.
I confirm this is still broken. 1. I moved .local/share/kscreen to kscreen.bak. 2. I reboot, log back in, set the 2nd monitor to portrait (vertical) in Settings->Display Configuration, I confirm to keep setting. 3. Log out. The 2nd monitor reverts back to landscape (horizontal). 4. I log back in and the 2nd monitor is still in landscape mode. Also the .local/share/kscreen is not recreated by KDE. Do I need to mkdir .local/share/kscreen so KDE can actually store the display settings? KDE Plasma 5.26.1 Frameworks 5.99.0 Qt 5.15.6 X11
I just tried with mkdir .local/share/kscreen nothing gets ever added there. Actually, it makes no difference whatsoever if there's a .local/share/kscreen dir or not. The monitor reverts to landscape the moment I log out and will stay like this after logging back in. I'm tired with this issue that's been going on for months now, so I just run the following command to spare myself editing the display setting every time I log in: xrandr --output DisplayPort-1 --rotate right --left-of DisplayPort-2 --output DisplayPort-2 --rotate normal --primary Though I still have the issue to resize and move all windows again back to where they are supposed to be.
I think I solved it. It's an issue with SDDM, it is not following the monitor settings from the user KDE session and the KDE session just reuse whatever setting the monitor are set on from SDDM. So to fix it, as root: cat >> /etc/sddm.conf.d/login-screen.conf [X11] DisplayCommand=/usr/share/sddm/scripts/Xsetup Ctrl+D cat >> /usr/share/sddm/scripts/Xsetup xrandr --output DisplayPort-1 --rotate right --left-of DisplayPort-2 --output DisplayPort-2 --rotate normal --primary Ctrl+D and bob is your uncle
This sounds more like KScreen isn't running at all. Under Startup and Shudown -> Background Services in system settings, is KScreen 2 marked as running?
(In reply to Zamundaaa from comment #14) > This sounds more like KScreen isn't running at all. Under Startup and > Shudown -> Background Services in system settings, is KScreen 2 marked as > running? you're right. it wasn't enabled. Has kscreen got any purpose other than monitors settings? I fixed the problem through sddm config so I'd rather avoid running redundant services.
It does screen settings, nothing else
So this is marked resolved but the user still has to run a command to fix? Am I following this thread right?
No, you're not following this right. If you disable the service that takes care of display settings, then it should not be a surprise if nothing takes care of the display settings anymore.
But I did no such thing. This happened (haven't tried KDE in a while) with every fresh install of KDE. I did no commands - nothing prior. It just never worked even on a fresh install. Gave up using KDE after being tired of being hopeful with every new release only to find it still not fixed.
Then you have a different bug. Can you check if the ~/.local/share/kscreen folder gets created for you after changing the display settings?
You're saying that KScreen isn't running on every KDE installation you've ever made?
(In reply to Nate Graham from comment #21) > You're saying that KScreen isn't running on every KDE installation you've > ever made? Ok so I was away from my desktop for a few weeks. But I have returned. I re-installed with the latest ISO of manjaro kde fresh on my computer. I first thought to try setting up my display layout under xOrg as that's what is shipped/enabled by default. However upon rebooting I observed a new behavior. Not only did it not keep my layout but this time it kept the portrait monitor in portrait mode but my landscape monitors were set to portrait as well... I checked your folder and that folder did exist. I of course tried again but same results. I then installed via the software UI the wayland components, rebooted, and logged in via Wayland. The behavior was the exact same as xOrg. Again I attempted it a 2nd time but the layout did not stick. This is even more strange as the middle monitor (which is landscape) is the primary but my guess is the reason why the landscape monitors go to portrait is because I switched display port connections on my gcp since last time I tried it. Before it was the portrait monitor that would not stay in portrait.
Yes unfortunately your screen settings will change when you go from X11 to Wayland and vice versa; that's a separate known issue tracked at Bug 429236. Can you commit to staying with either X1 or Wayland for a moment while we debug? First I need to you make the monitor arrangement the way you like it. Then paste the output of `kscreen-doctor -o` here. Then reboot so it gets messed up again, and then paste the output of `kscreen-doctor -o` here again. Can you do that? Thanks a lot!
(In reply to Nate Graham from comment #23) > Yes unfortunately your screen settings will change when you go from X11 to > Wayland and vice versa; that's a separate known issue tracked at Bug 429236. > > Can you commit to staying with either X1 or Wayland for a moment while we > debug? > > First I need to you make the monitor arrangement the way you like it. Then > paste the output of `kscreen-doctor -o` here. Then reboot so it gets messed > up again, and then paste the output of `kscreen-doctor -o` here again. Can > you do that? Thanks a lot! Sure thing! I'll get you that information tonight. Away from desktop at the moment. I live in mountain time in the US.
Output: 1 Hypercope Gmbh Aachen DP-1-PX7 Prime enabled connected primary DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@165* 2:2560x1440@144 3:2560x1440@120 4:2560x1440@75 5:1920x1200@60 6:1920x1080@60 7:1920x1080@60 8:1600x1200@60 9:1680x1050@60 10:1400x1050@60 11:1600x900@60 12:1280x1024@75 13:1280x1024@60 14:1440x900@60 15:1280x960@60 16:1280x800@60 17:1152x864@60 18:1280x720@60 19:1024x768@75 20:1024x768@70 21:1024x768@60 22:800x600@75 23:800x600@72 24:800x600@60 25:640x480@75 26:640x480@73 27:640x480@60 28:640x480@60 29:640x480@60 30:720x400@70 Geometry: 2560,672 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Automatic RgbRange: unknown primary Output: 2 Hypercope Gmbh Aachen DP-2-PX7 Prime enabled connected DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@165* 2:2560x1440@144 3:2560x1440@120 4:2560x1440@75 5:1920x1200@60 6:1920x1080@60 7:1920x1080@60 8:1600x1200@60 9:1680x1050@60 10:1400x1050@60 11:1600x900@60 12:1280x1024@75 13:1280x1024@60 14:1440x900@60 15:1280x960@60 16:1280x800@60 17:1152x864@60 18:1280x720@60 19:1024x768@75 20:1024x768@70 21:1024x768@60 22:800x600@75 23:800x600@72 24:800x600@60 25:640x480@75 26:640x480@73 27:640x480@60 28:640x480@60 29:640x480@60 30:720x400@70 Geometry: 0,672 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Automatic RgbRange: unknown Output: 3 Hypercope Gmbh Aachen DP-3-PX7 Prime enabled connected DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@165* 2:2560x1440@144 3:2560x1440@120 4:2560x1440@75 5:1920x1200@60 6:1920x1080@60 7:1920x1080@60 8:1600x1200@60 9:1680x1050@60 10:1400x1050@60 11:1600x900@60 12:1280x1024@75 13:1280x1024@60 14:1440x900@60 15:1280x960@60 16:1280x800@60 17:1152x864@60 18:1280x720@60 19:1024x768@75 20:1024x768@70 21:1024x768@60 22:800x600@75 23:800x600@72 24:800x600@60 25:640x480@75 26:640x480@73 27:640x480@60 28:640x480@60 29:640x480@60 30:720x400@70 Geometry: 5120,0 1440x2560 Scale: 1 Rotation: 8 Overscan: 0 Vrr: Automatic RgbRange: unknown
Output: 1 Hypercope Gmbh Aachen DP-1-PX7 Prime enabled connected primary DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@165* 2:2560x1440@144 3:2560x1440@120 4:2560x1440@75 5:1920x1200@60 6:1920x1080@60 7:1920x1080@60 8:1600x1200@60 9:1680x1050@60 10:1400x1050@60 11:1600x900@60 12:1280x1024@75 13:1280x1024@60 14:1440x900@60 15:1280x960@60 16:1280x800@60 17:1152x864@60 18:1280x720@60 19:1024x768@75 20:1024x768@70 21:1024x768@60 22:800x600@75 23:800x600@72 24:800x600@60 25:640x480@75 26:640x480@73 27:640x480@60 28:640x480@60 29:640x480@60 30:720x400@70 Geometry: 2560,672 1440x2560 Scale: 1 Rotation: 8 Overscan: 0 Vrr: Automatic RgbRange: unknown primary Output: 2 Hypercope Gmbh Aachen DP-2-PX7 Prime enabled connected DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@165* 2:2560x1440@144 3:2560x1440@120 4:2560x1440@75 5:1920x1200@60 6:1920x1080@60 7:1920x1080@60 8:1600x1200@60 9:1680x1050@60 10:1400x1050@60 11:1600x900@60 12:1280x1024@75 13:1280x1024@60 14:1440x900@60 15:1280x960@60 16:1280x800@60 17:1152x864@60 18:1280x720@60 19:1024x768@75 20:1024x768@70 21:1024x768@60 22:800x600@75 23:800x600@72 24:800x600@60 25:640x480@75 26:640x480@73 27:640x480@60 28:640x480@60 29:640x480@60 30:720x400@70 Geometry: 0,672 1440x2560 Scale: 1 Rotation: 8 Overscan: 0 Vrr: Automatic RgbRange: unknown Output: 3 Hypercope Gmbh Aachen DP-3-PX7 Prime enabled connected DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@165* 2:2560x1440@144 3:2560x1440@120 4:2560x1440@75 5:1920x1200@60 6:1920x1080@60 7:1920x1080@60 8:1600x1200@60 9:1680x1050@60 10:1400x1050@60 11:1600x900@60 12:1280x1024@75 13:1280x1024@60 14:1440x900@60 15:1280x960@60 16:1280x800@60 17:1152x864@60 18:1280x720@60 19:1024x768@75 20:1024x768@70 21:1024x768@60 22:800x600@75 23:800x600@72 24:800x600@60 25:640x480@75 26:640x480@73 27:640x480@60 28:640x480@60 29:640x480@60 30:720x400@70 Geometry: 5120,0 1440x2560 Scale: 1 Rotation: 8 Overscan: 0 Vrr: Automatic RgbRange: unknown
Done. Sorry, I had a really busy past few days. But this is important to me that this gets fixed. :) Hope this helps.
So DP-1-PX7 and DP-2-PX7 have had their Geometry: and Rotation: properties reset. Thanks
Created attachment 153750 [details] Screenshot of Monitors after reboot or log-off/log-in Yeah the attached image is what happens. The vertical monitor on my right stays in portrait. What's interesting though, earlier this year when I was using Manjaro KDE as my primary linux distro, the vertical one would go to landscape after every reboot and the horizontal monitors would stay on landscape. Now, maybe because I moved and reconnected things to different ports on my GPU, it's the vertical that stays in portrait but my horizonal monitors go into portrait. My middle one was always been my primary display.
> Now, maybe because I moved and reconnected things to different ports on my GPU Yep, quite related.
(In reply to Nate Graham from comment #30) > > Now, maybe because I moved and reconnected things to different ports on my GPU > Yep, quite related. Hey Nate, The short of it, behavior is still the same (broken multi-monitor support) I reinstalled Manjaro KDE after having been on just Windows for sometime. With the latest news on Plasma 27 I thought I'd give my multimonitor setup another try with KDE. First off, Plasma 26 didn't fix it because at the time anyway I installed it this week it still only shipped with Plasma 26. I joined the unstable branch, got the Plasma 27 updates, and the exact same behavior remained. I was quite disappointed especially given all the hype that 27 fixes a lot of multi-monitor issues.
Sorry to hear that. Can you paste the output of `kscreen-doctor -o` before rebooting, and afterwards?
(In reply to Nate Graham from comment #32) > Sorry to hear that. > > Can you paste the output of `kscreen-doctor -o` before rebooting, and > afterwards? Here you go. Before Reboot KScreen-Doctor Ouput with Screens Aligned correctly: Output: 1 DP-1 enabled connected priority 1 DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@165* 2:2560x1440@144 3:2560x1440@120 4:2560x1440@75 5:1920x1200@60 6:1920x1080@60 7:1920x1080@60 8:1600x1200@60 9:1680x1050@60 10:1400x1050@60 11:1600x900@60 12:1280x1024@75 13:1280x1024@60 14:1440x900@60 15:1280x960@60 16:1280x800@60 17:1152x864@60 18:1280x720@60 19:1024x768@75 20:1024x768@70 21:1024x768@60 22:800x600@75 23:800x600@72 24:800x600@60 25:640x480@75 26:640x480@73 27:640x480@60 28:640x480@60 29:640x480@60 30:720x400@70 31:1600x1200@60 32:1280x1024@60 33:1024x768@60 34:1920x1200@60 35:2560x1440@60 36:1920x1080@60 37:1600x900@60 38:1368x768@60 39:1280x720@60 Geometry: 2560,560 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Automatic RgbRange: unknown Output: 2 DP-2 enabled connected priority 2 DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@165* 2:2560x1440@144 3:2560x1440@120 4:2560x1440@75 5:1920x1200@60 6:1920x1080@60 7:1920x1080@60 8:1600x1200@60 9:1680x1050@60 10:1400x1050@60 11:1600x900@60 12:1280x1024@75 13:1280x1024@60 14:1440x900@60 15:1280x960@60 16:1280x800@60 17:1152x864@60 18:1280x720@60 19:1024x768@75 20:1024x768@70 21:1024x768@60 22:800x600@75 23:800x600@72 24:800x600@60 25:640x480@75 26:640x480@73 27:640x480@60 28:640x480@60 29:640x480@60 30:720x400@70 31:1600x1200@60 32:1280x1024@60 33:1024x768@60 34:1920x1200@60 35:2560x1440@60 36:1920x1080@60 37:1600x900@60 38:1368x768@60 39:1280x720@60 Geometry: 0,560 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Automatic RgbRange: unknown Output: 3 DP-3 enabled connected priority 3 DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@165* 2:2560x1440@144 3:2560x1440@120 4:2560x1440@75 5:1920x1200@60 6:1920x1080@60 7:1920x1080@60 8:1600x1200@60 9:1680x1050@60 10:1400x1050@60 11:1600x900@60 12:1280x1024@75 13:1280x1024@60 14:1440x900@60 15:1280x960@60 16:1280x800@60 17:1152x864@60 18:1280x720@60 19:1024x768@75 20:1024x768@70 21:1024x768@60 22:800x600@75 23:800x600@72 24:800x600@60 25:640x480@75 26:640x480@73 27:640x480@60 28:640x480@60 29:640x480@60 30:720x400@70 31:1600x1200@60 32:1280x1024@60 33:1024x768@60 34:1920x1200@60 35:2560x1440@60 36:1920x1080@60 37:1600x900@60 38:1368x768@60 39:1280x720@60 Geometry: 5120,0 1440x2560 Scale: 1 Rotation: 8 Overscan: 0 Vrr: Automatic RgbRange: unknown After Reboot KScreen-Doctor Ouput with Screen Miss-aligned: Output: 1 DP-1 enabled connected priority 1 DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@165* 2:2560x1440@144 3:2560x1440@120 4:2560x1440@75 5:1920x1200@60 6:1920x1080@60 7:1920x1080@60 8:1600x1200@60 9:1680x1050@60 10:1400x1050@60 11:1600x900@60 12:1280x1024@75 13:1280x1024@60 14:1440x900@60 15:1280x960@60 16:1280x800@60 17:1152x864@60 18:1280x720@60 19:1024x768@75 20:1024x768@70 21:1024x768@60 22:800x600@75 23:800x600@72 24:800x600@60 25:640x480@75 26:640x480@73 27:640x480@60 28:640x480@60 29:640x480@60 30:720x400@70 31:1600x1200@60 32:1280x1024@60 33:1024x768@60 34:1920x1200@60 35:2560x1440@60 36:1920x1080@60 37:1600x900@60 38:1368x768@60 39:1280x720@60 Geometry: 2560,560 1440x2560 Scale: 1 Rotation: 8 Overscan: 0 Vrr: Automatic RgbRange: unknown Output: 2 DP-2 enabled connected priority 2 DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@165* 2:2560x1440@144 3:2560x1440@120 4:2560x1440@75 5:1920x1200@60 6:1920x1080@60 7:1920x1080@60 8:1600x1200@60 9:1680x1050@60 10:1400x1050@60 11:1600x900@60 12:1280x1024@75 13:1280x1024@60 14:1440x900@60 15:1280x960@60 16:1280x800@60 17:1152x864@60 18:1280x720@60 19:1024x768@75 20:1024x768@70 21:1024x768@60 22:800x600@75 23:800x600@72 24:800x600@60 25:640x480@75 26:640x480@73 27:640x480@60 28:640x480@60 29:640x480@60 30:720x400@70 31:1600x1200@60 32:1280x1024@60 33:1024x768@60 34:1920x1200@60 35:2560x1440@60 36:1920x1080@60 37:1600x900@60 38:1368x768@60 39:1280x720@60 Geometry: 0,560 1440x2560 Scale: 1 Rotation: 8 Overscan: 0 Vrr: Automatic RgbRange: unknown Output: 3 DP-3 enabled connected priority 3 DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@165* 2:2560x1440@144 3:2560x1440@120 4:2560x1440@75 5:1920x1200@60 6:1920x1080@60 7:1920x1080@60 8:1600x1200@60 9:1680x1050@60 10:1400x1050@60 11:1600x900@60 12:1280x1024@75 13:1280x1024@60 14:1440x900@60 15:1280x960@60 16:1280x800@60 17:1152x864@60 18:1280x720@60 19:1024x768@75 20:1024x768@70 21:1024x768@60 22:800x600@75 23:800x600@72 24:800x600@60 25:640x480@75 26:640x480@73 27:640x480@60 28:640x480@60 29:640x480@60 30:720x400@70 31:1600x1200@60 32:1280x1024@60 33:1024x768@60 34:1920x1200@60 35:2560x1440@60 36:1920x1080@60 37:1600x900@60 38:1368x768@60 39:1280x720@60 Geometry: 5120,0 1440x2560 Scale: 1 Rotation: 8 Overscan: 0 Vrr: Automatic RgbRange: unknown
(In reply to Nate Graham from comment #32) > Sorry to hear that. > > Can you paste the output of `kscreen-doctor -o` before rebooting, and > afterwards? Here is some more info. Hope it helps. Night, I go to work tomorrow to do web dev but I hope this help. https://imgur.com/a/j8Wpa9R
So the DP-1 and DP-2 screens are changing from > 1440x2560 Scale: 1 Rotation: 8 to > 2560x1440 Scale: 1 Rotation: 1 Thanks. What are the serial numbers of the screens? Do they by any chance happen to be identical?
(In reply to Nate Graham from comment #35) > So the DP-1 and DP-2 screens are changing from > > 1440x2560 Scale: 1 Rotation: 8 > to > > 2560x1440 Scale: 1 Rotation: 1 > Thanks. > > What are the serial numbers of the screens? Do they by any chance happen to > be identical? All three montiors are the same. This is what they are. Bought them right before Covid craziness November 2019. Newer Pixio 1440p models have since replaced what I have but these still work well! :) https://www.newegg.com/p/N82E16824737006?Item=N82E16824737006 They show up as the same name in the display configuration (see link). When I hit identify button it will each read out as: "Hypercope Gmbh Aaachen DP-1-PX7 Prime", "Hypercope Gmbh Aaachen DP-2-PX7 Prime", and "Hypercope Gmbh Aaachen DP-3-PX7 Prime" on the respective monitor. https://imgur.com/a/j02VMiZ I can look at the serial numbers on the back of the monitor when I am home tonight to see if they all match - unless there's an easy way to do it with software that I don't know about. What's funny is I bought these three monitors in part believing it would likely have less issues if they were all the same. Thanks, really really appreciate you looking into this. I obviously really want to see this get resolved because I like Linux and would like to daily drive it. Gnome doesn't work for me for a number of reasons but KDE is pretty much there for me, minus this really annoying issue.
No problem, happy to help! If you run `kscreen-console bug`, and then paste the contents of the "EDID:" blocks (one per monitor) that would be nice. The serial numbers are buried in those blocks. Basically I want to see if each monitor is using the same serial number, which would suck. There's also the case where each one has a serial number that's one digit different from the others, in which this would be Bug 466136 which is fixed for Plasma 5.27.2.
(In reply to Nate Graham from comment #37) > No problem, happy to help! > > If you run `kscreen-console bug`, and then paste the contents of the "EDID:" > blocks (one per monitor) that would be nice. The serial numbers are buried > in those blocks. Basically I want to see if each monitor is using the same > serial number, which would suck. There's also the case where each one has a > serial number that's one digit different from the others, in which this > would be Bug 466136 which is fixed for Plasma 5.27.2. That sounds hopeful. Here you go. But looks like they are the same...am I hosed? EDID Info: Device ID: "xrandr-Hypercope Gmbh Aachen-PX7 Prime" Name: "PX7 Prime" Vendor: "Hypercope Gmbh Aachen" Serial: "" EISA ID: "" Hash: "45b764cde5ed146a61f45909c452c6e2" Width: 60 Height: 34 Gamma: 2.2 Red: QQuaternion(scalar:1, vector:(0.677734, 0.308594, 0)) Green: QQuaternion(scalar:1, vector:(0.265625, 0.663086, 0)) Blue: QQuaternion(scalar:1, vector:(0.148438, 0.0527344, 0)) White: QQuaternion(scalar:1, vector:(0.313477, 0.329102, 0)) EDID Info: Device ID: "xrandr-Hypercope Gmbh Aachen-PX7 Prime" Name: "PX7 Prime" Vendor: "Hypercope Gmbh Aachen" Serial: "" EISA ID: "" Hash: "45b764cde5ed146a61f45909c452c6e2" Width: 60 Height: 34 Gamma: 2.2 Red: QQuaternion(scalar:1, vector:(0.677734, 0.308594, 0)) Green: QQuaternion(scalar:1, vector:(0.265625, 0.663086, 0)) Blue: QQuaternion(scalar:1, vector:(0.148438, 0.0527344, 0)) White: QQuaternion(scalar:1, vector:(0.313477, 0.329102, 0)) EDID Info: Device ID: "xrandr-Hypercope Gmbh Aachen-PX7 Prime" Name: "PX7 Prime" Vendor: "Hypercope Gmbh Aachen" Serial: "" EISA ID: "" Hash: "45b764cde5ed146a61f45909c452c6e2" Width: 60 Height: 34 Gamma: 2.2 Red: QQuaternion(scalar:1, vector:(0.677734, 0.308594, 0)) Green: QQuaternion(scalar:1, vector:(0.265625, 0.663086, 0)) Blue: QQuaternion(scalar:1, vector:(0.148438, 0.0527344, 0)) White: QQuaternion(scalar:1, vector:(0.313477, 0.329102, 0))
Oh wait...The serial is blank... I was looking at the Hash. I'mma check the back of my monitors now.
And here you have it. No serial number on the stickers... How the f do they get away with that in the US? Am I seriously going to have to buy new monitors to use KDE? Gnome doesn't have this issue or Windows. Maybe because they just look at display port connections on the GPU? I'm so disappointed... https://imgur.com/a/MbJvZiE
So we're in an unfortunate situation: your monitors can't be identified by name, resolution, or serial number, All we have is the connector ID to distinguish them, but since you're using an AMD GPU, the connector ID changes on boot due to https://bugzilla.kernel.org/show_bug.cgi?id=206387. So we effectively have no way to distinguish the screens! I wonder, have you ever used these screens on GNOME or Windows or any other environment? Are they identified correctly there?
Sorry, missed the part about this working properly in GNOME and Windows. So there must be some other bit of data we can use here...
(In reply to Nate Graham from comment #42) > Sorry, missed the part about this working properly in GNOME and Windows. So > there must be some other bit of data we can use here... Yeah... On a side note, I just heard back from Pixio 2 minutes ago. Perfect timing :) I put in a support ticket this weekend about no product number on my monitors. This was their reply. "Hello Joel, Thank you for reaching out to us. I apologize for the delayed response; we are closed on weekends. Unfortunately, the factory that produced the PX7 Prime shut down years ago and never made a firmware update for this model, so the PX7 Prime has no firmware updates. In terms of the serial number, it should the 6 or 7 digit line of numbers on the label on the back of the monitor." So yeah, hopefully that AMD bug you listed gets resolved as looks like I can't get any firmware update that will have the product number added. I'm pretty disappointed. Looks like I am stuck in Windows land indefinitely, until this gets fixed, gnome gets better, or I buy new monitors (I like to wait at least 5 years at the minimum before buying new monitors and it's only been 3 since I got these).
There may be bugs in our code that are exacerbating the issue anyway. Let's see what we can do about it. Hopefully you won't need to buy new screens or avoid Plasma!
If you select "Save displays' properties: For only this specific display arrangement" in the display settings, does the rotation still reset?
A possibly relevant merge request was started @ https://invent.kde.org/plasma/kscreen/-/merge_requests/187
(In reply to Zamundaaa from comment #45) > If you select "Save displays' properties: For only this specific display > arrangement" in the display settings, does the rotation still reset? So I went home and tried it over lunch. Toggled that global radio button you mentioned & it works! The only thing still off is the login screen. On reboot, it will still show my right monitor in landscape, but once I login it goes to portrait like I had configured it :) Definitely usable now!
(In reply to Nate Graham from comment #44) > There may be bugs in our code that are exacerbating the issue anyway. Let's > see what we can do about it. Hopefully you won't need to buy new screens or > avoid Plasma! Thanks for your help! @Zamundaaa suggested a work around that worked :)
(In reply to Nate Graham from comment #44) > There may be bugs in our code that are exacerbating the issue anyway. Let's > see what we can do about it. Hopefully you won't need to buy new screens or > avoid Plasma! I'd probably still keep this ticket open because it's not a great out of the box experience. Especially if your landscape monitors (one being primary) are the ones being reset to portrait. But I'm super pleased there is a work around. Does have me interested still on how Windows & Gnome is able to just work out of the box with my monitors - maybe they are doing the same thing or windows at least relies on the dp #. Pretty Windows does the former because when clicking "Identify" it shows just numbers which is way more helpful in my case because what currently displays in KDE when clicking identify is the same name on all 3 with no number so hard to know which is which.
(In reply to Nate Graham from comment #44) > There may be bugs in our code that are exacerbating the issue anyway. Let's > see what we can do about it. Hopefully you won't need to buy new screens or > avoid Plasma! I'd probably still keep this ticket open because it's not a great out of the box experience. Especially if your landscape monitors (one being primary) are the ones being reset to portrait. But I'm super pleased there is a work around. Does have me interested still on how Windows & Gnome is able to just work out of the box with my monitors - maybe they are doing the same thing or windows at least relies on the dp #. Pretty Windows does the former because when clicking "Identify" it shows just numbers which is way more helpful in my case because what currently displays in KDE when clicking identify is the same name on all 3 with no number so hard to know which is which.(In reply to mr.jwluthi from comment #49) > (In reply to Nate Graham from comment #44) > > There may be bugs in our code that are exacerbating the issue anyway. Let's > > see what we can do about it. Hopefully you won't need to buy new screens or > > avoid Plasma! > > I'd probably still keep this ticket open because it's not a great out of the > box experience. Especially if your landscape monitors (one being primary) > are the ones being reset to portrait. But I'm super pleased there is a work > around. Does have me interested still on how Windows & Gnome is able to just > work out of the box with my monitors - maybe they are doing the same thing > or windows at least relies on the dp #. > > Pretty Windows does the former because when clicking "Identify" it shows > just numbers which is way more helpful in my case because what currently > displays in KDE when clicking identify is the same name on all 3 with no > number so hard to know which is which. Sorry, the later* (not former) but you get my drift.
Yes, is definitely seems like there's a code problem with how KScreen handles this specific use case; see the linked merge request. I'd be interested in seeing a screenshot of the numbers you see on Windows.
(In reply to Nate Graham from comment #51) > Yes, is definitely seems like there's a code problem with how KScreen > handles this specific use case; see the linked merge request. > > I'd be interested in seeing a screenshot of the numbers you see on Windows. I'm on my work PC now back at work. But this is what I was referring to. Same thing would happen on my home PC when running Windows. It's much more helpful than just the monitor name that only KDE gives for their Identify feature. Anyway, I know this is out of scope of this ticket but just some (hopefully) valuable user feedback :) . Understand this may be a current limitation due to KDE not looking at port numbers but PN's. https://imgur.com/a/QSw8SBD
*** Bug 466187 has been marked as a duplicate of this bug. ***
Git commit e19e157c314fdf4bbd1262ada7d3c3842fce149b by Xaver Hugl. Committed on 13/03/2023 at 16:19. Pushed by zamundaaa into branch 'master'. kded/output: with duplicate edid hashes, use different global config files Before this commit, the global config files for two outputs with the same hash would override each other, making KScreen lose some settings after a reboot. With this commit, it will detect that and append the connector name to the file name instead, thus separating the settings for the outputs properly. Related: bug 448599 M +7 -1 kded/config.cpp M +29 -23 kded/output.cpp M +1 -2 kded/output.h M +3 -3 tests/kded/testgenerator.cpp https://invent.kde.org/plasma/kscreen/commit/e19e157c314fdf4bbd1262ada7d3c3842fce149b
Git commit 8288ea632f344472241ef107732c62757a8af2c9 by Xaver Hugl. Committed on 13/03/2023 at 16:34. Pushed by zamundaaa into branch 'Plasma/5.27'. kded/output: with duplicate edid hashes, use different global config files Before this commit, the global config files for two outputs with the same hash would override each other, making KScreen lose some settings after a reboot. With this commit, it will detect that and append the connector name to the file name instead, thus separating the settings for the outputs properly. Related: bug 448599 (cherry picked from commit e19e157c314fdf4bbd1262ada7d3c3842fce149b) M +7 -1 kded/config.cpp M +29 -23 kded/output.cpp M +1 -2 kded/output.h M +3 -3 tests/kded/testgenerator.cpp https://invent.kde.org/plasma/kscreen/commit/8288ea632f344472241ef107732c62757a8af2c9