466187 – Screen priorities get scrambled after switching to a TTY and back

Bug 466187 - Screen priorities get scrambled after switching to a TTY and back

Summary: Screen priorities get scrambled after switching to a TTY and back

Status:	RESOLVED DUPLICATE of bug 452614

Alias:	None

Product:	KScreen
Classification:	Plasma
Component:	common (show other bugs)
Version:	5.27.1
Platform:	Arch Linux Linux

Importance:	NOR normal
Target Milestone:	---
Assignee:	kscreen-bugs-null@kde.org

URL:
Keywords:

Depends on:
Blocks:

Reported:	2023-02-21 10:06 UTC by hendrik.frueh
Modified:	2023-03-01 15:34 UTC (History)
CC List:	1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.

Description hendrik.frueh 2023-02-21 10:06:10 UTC

SUMMARY
I'm using wayland with a three monitor setup, where the middle one (DP-2) is the primary monitor. When switching to a TTY and back, the monitor on the right (DP-1) gets set as primary. This also overrides my manually set screen priorities in the system settings.

STEPS TO REPRODUCE
1. Set screen priorities manually
2. Switch to a TTY 
3. Switch back to tty1

OBSERVED RESULT
Screen priorities change, making another screen primary.

EXPECTED RESULT
Screen priorities don't change.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.0
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.12-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 2600 Six-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2

ADDITIONAL INFORMATION
Output of "kscreen-doctor -o" before switching to a TTY:
Output: 1 HDMI-A-1 enabled connected priority 3 HDMI Modes: 0:1680x1050@60*! 1:1920x1080@60 2:1920x1080@50 3:1280x1024@60 4:1440x900@60 5:1280x960@60 6:1280x800@60 7:1280x720@60 8:1280x720@60 9:1280x720@50 10:1024x768@75 11:1024x768@70 12:1024x768@60 13:800x600@75 14:800x600@72 15:800x600@60 16:800x600@56 17:720x576@50 18:720x480@60 19:640x480@75 20:640x480@73 21:640x480@60 22:640x480@60 23:1280x1024@60 24:1024x768@60 25:1600x900@60 26:1368x768@60 27:1280x720@60 Geometry: 0,380 2240x1400 Scale: 0.75 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown
Output: 2 DP-1 enabled connected priority 2 DisplayPort Modes: 0:2560x1440@144*! 1:2560x1440@120 2:2560x1440@60 3:2560x1440@60 4:1920x1080@120 5:1920x1080@60 6:1920x1080@60 7:1920x1080@50 8:1680x1050@60 9:1280x1024@75 10:1280x1024@60 11:1440x900@60 12:1280x960@60 13:1280x800@60 14:1152x864@75 15:1280x720@60 16:1280x720@60 17:1280x720@50 18:1024x768@75 19:1024x768@70 20:1024x768@60 21:800x600@75 22:800x600@72 23:800x600@60 24:800x600@56 25:720x576@50 26:720x480@60 27:640x480@75 28:640x480@73 29:640x480@60 30:1600x1200@60 31:1280x1024@60 32:1024x768@60 33:1920x1200@60 34:2560x1440@60 35:1920x1080@60 36:1600x900@60 37:1368x768@60 38:1280x720@60 Geometry: 6080,360 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown
Output: 3 DP-2 enabled connected priority 1 DisplayPort Modes: 0:3840x2160@60*! 1:3840x2160@60 2:3840x2160@50 3:3840x2160@30 4:3840x2160@30 5:3840x2160@25 6:3840x2160@24 7:2560x1600@60 8:2560x1440@60 9:1920x1080@60 10:1920x1080@60 11:1920x1080@50 12:1920x1080@30 13:1920x1080@25 14:1920x1080@24 15:1680x1050@60 16:1600x900@60 17:1280x1024@75 18:1280x1024@60 19:1280x800@60 20:1280x720@60 21:1280x720@60 22:1280x720@50 23:1024x768@75 24:1024x768@60 25:800x600@75 26:800x600@60 27:720x576@50 28:720x480@60 29:640x480@75 30:640x480@60 31:640x480@60 32:1600x1200@60 33:1280x1024@60 34:1024x768@60 35:2560x1600@60 36:1920x1200@60 37:3200x1800@60 38:2880x1620@60 39:2560x1440@60 40:1920x1080@60 41:1600x900@60 42:1368x768@60 43:1280x720@60 Geometry: 2240,0 3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown


Output of "kscreen-doctor -o" after switching to a TTY:
Output: 1 HDMI-A-1 enabled connected priority 3 HDMI Modes: 0:1680x1050@60*! 1:1920x1080@60 2:1920x1080@50 3:1280x1024@60 4:1440x900@60 5:1280x960@60 6:1280x800@60 7:1280x720@60 8:1280x720@60 9:1280x720@50 10:1024x768@75 11:1024x768@70 12:1024x768@60 13:800x600@75 14:800x600@72 15:800x600@60 16:800x600@56 17:720x576@50 18:720x480@60 19:640x480@75 20:640x480@73 21:640x480@60 22:640x480@60 23:1280x1024@60 24:1024x768@60 25:1600x900@60 26:1368x768@60 27:1280x720@60 Geometry: 0,380 2240x1400 Scale: 0.75 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown
Output: 2 DP-1 enabled connected priority 1 DisplayPort Modes: 0:2560x1440@144*! 1:2560x1440@120 2:2560x1440@60 3:2560x1440@60 4:1920x1080@120 5:1920x1080@60 6:1920x1080@60 7:1920x1080@50 8:1680x1050@60 9:1280x1024@75 10:1280x1024@60 11:1440x900@60 12:1280x960@60 13:1280x800@60 14:1152x864@75 15:1280x720@60 16:1280x720@60 17:1280x720@50 18:1024x768@75 19:1024x768@70 20:1024x768@60 21:800x600@75 22:800x600@72 23:800x600@60 24:800x600@56 25:720x576@50 26:720x480@60 27:640x480@75 28:640x480@73 29:640x480@60 30:1600x1200@60 31:1280x1024@60 32:1024x768@60 33:1920x1200@60 34:2560x1440@60 35:1920x1080@60 36:1600x900@60 37:1368x768@60 38:1280x720@60 Geometry: 6080,360 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown
Output: 3 DP-2 enabled connected priority 2 DisplayPort Modes: 0:3840x2160@60*! 1:3840x2160@60 2:3840x2160@50 3:3840x2160@30 4:3840x2160@30 5:3840x2160@25 6:3840x2160@24 7:2560x1600@60 8:2560x1440@60 9:1920x1080@60 10:1920x1080@60 11:1920x1080@50 12:1920x1080@30 13:1920x1080@25 14:1920x1080@24 15:1680x1050@60 16:1600x900@60 17:1280x1024@75 18:1280x1024@60 19:1280x800@60 20:1280x720@60 21:1280x720@60 22:1280x720@50 23:1024x768@75 24:1024x768@60 25:800x600@75 26:800x600@60 27:720x576@50 28:720x480@60 29:640x480@75 30:640x480@60 31:640x480@60 32:1600x1200@60 33:1280x1024@60 34:1024x768@60 35:2560x1600@60 36:1920x1200@60 37:3200x1800@60 38:2880x1620@60 39:2560x1440@60 40:1920x1080@60 41:1600x900@60 42:1368x768@60 43:1280x720@60 Geometry: 2240,0 3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown

Comment 1 Nate Graham 2023-02-23 00:42:16 UTC

The output of `kscreen-doctor-o` is the same in the before and after; both say that HDMI-A-1 is the primary.

Is this the way it actually is, or was that a copy-paste error?

Comment 2 hendrik.frueh 2023-02-23 09:42:25 UTC

(In reply to Nate Graham from comment #1)
> The output of `kscreen-doctor-o` is the same in the before and after; both
> say that HDMI-A-1 is the primary.
> 
> Is this the way it actually is, or was that a copy-paste error?

My impression is that 1 is the highest and 3 the lowest priority, since DP-2 starts with prio 1 (as well as showing my panels and being at the top of the priority list in the system settings) and DP-1 with prio 2. After switching to some tty and back, DP-2 and DP-1 swap their priorities and my panels change the screen accordingly. HDMI-A-1 always stays at prio 3.



I also just reproduced this on 5.27.1. Truncated outputs of "kscreen-doctor -o" for more clarity:
Before:
Output: 1 HDMI-A-1 enabled connected priority 3 HDMI Modes: ...
Output: 2 DP-1 enabled connected priority 2 DisplayPort Modes: ...
Output: 3 DP-2 enabled connected priority 1 DisplayPort Modes: ...

After:
Output: 1 HDMI-A-1 enabled connected priority 3 HDMI Modes: ...
Output: 2 DP-1 enabled connected priority 1 DisplayPort Modes: ...
Output: 3 DP-2 enabled connected priority 2 DisplayPort Modes: ...



"kscreen-console monitor" also shows the change:

Priorities changed: QMap((1, KScreen::Output(1, "HDMI-A-1", connected enabled priority 3, pos: QPoint(0,380), res: QSize(1680, 1050), modeId: "0", scale: 0.75, clone: no, rotation: KScreen::Output::None, followPreferredMode: false))(2, KScreen::Output(2, "DP-1", connected enabled priority 1, pos: QPoint(6080,360), res: QSize(2560, 1440), modeId: "0", scale: 1, clone: no, rotation: KScreen::Output::None, followPreferredMode: false))(3, KScreen::Output(3, "DP-2", connected enabled priority 2, pos: QPoint(2240,0), res: QSize(3840, 2160), modeId: "0", scale: 1, clone: no, rotation: KScreen::Output::None, followPreferredMode: false)))
Initializing  "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"



I also gathered these snippets from journalctl and annotated them:

###### changing priorities to my config (decending in priority: DP-2 DP-1 HDMI-A-1) via systemsettings
Feb 23 10:23:15 PC-Linux systemd[809]: Started System Settings - System Settings.
Feb 23 10:23:21 PC-Linux plasmashell[1003]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Feb 23 10:23:21 PC-Linux plasmashell[1003]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Feb 23 10:23:21 PC-Linux plasmashell[1003]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Feb 23 10:23:21 PC-Linux plasmashell[1003]: Checking screens: available: (QScreen(0x56522dec1f10, name="DP-2"), QScreen(0x56522dec2210, name="DP-1"), QScreen(0x56522dec2f20, name="HDMI-A-1")) redundant: QHash() fake: QSet() all: (QScreen(0x56522dec2f20, name="HDMI-A-1"), QScreen(0x56522dec2210, name="DP-1"), QScreen(0x56522dec1f10, name="DP-2"))
Feb 23 10:23:21 PC-Linux kcminit[2938]: Initializing  "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Feb 23 10:23:21 PC-Linux kcminit[2949]: Initializing  "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Feb 23 10:23:21 PC-Linux kcminit[2939]: Initializing  "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Feb 23 10:23:21 PC-Linux kcminit[2953]: Initializing  "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
###### switching to tty3
Feb 23 10:27:22 PC-Linux kwin_wayland[895]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Feb 23 10:27:22 PC-Linux kwin_wayland[895]: kwin_wayland_drm: Presentation failed! Invalid argument
Feb 23 10:27:23 PC-Linux kwin_wayland[895]: kwin_core: Applying KScreen config failed!
Feb 23 10:27:23 PC-Linux kwin_wayland[895]: kwin_wayland_drm: Atomic commit failed! Permission denied
Feb 23 10:27:23 PC-Linux kwin_wayland[895]: kwin_wayland_drm: Presentation failed! Permission denied
Feb 23 10:27:23 PC-Linux plasmashell[1003]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Feb 23 10:27:23 PC-Linux plasmashell[1003]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Feb 23 10:27:23 PC-Linux plasmashell[1003]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Feb 23 10:27:23 PC-Linux plasmashell[1003]: Checking screens: available: (QScreen(0x56522dec2210, name="DP-1"), QScreen(0x56522dec1f10, name="DP-2"), QScreen(0x56522dec2f20, name="HDMI-A-1")) redundant: QHash() fake: QSet() all: (QScreen(0x56522dec2f20, name="HDMI-A-1"), QScreen(0x56522dec2210, name="DP-1"), QScreen(0x56522dec1f10, name="DP-2"))
Feb 23 10:27:23 PC-Linux kwin_wayland[895]: kwin_core: Applying KScreen config failed!
Feb 23 10:27:23 PC-Linux kdeconnectd[1163]: org.kde.pulseaudio: No object for name "alsa_output.usb-Kingston_HyperX_Cloud_II_Wireless_000000000001-00.analog-stereo"
Feb 23 10:27:23 PC-Linux kdeconnectd[1163]: org.kde.pulseaudio: No object for name "alsa_output.usb-Kingston_HyperX_Cloud_II_Wireless_000000000001-00.analog-stereo"
Feb 23 10:27:23 PC-Linux kdeconnectd[1163]: org.kde.pulseaudio: No object for name "alsa_input.usb-MICE_MICROPHONE_USB_MICROPHONE_201308-00.mono-fallback"
Feb 23 10:27:23 PC-Linux kdeconnectd[1163]: org.kde.pulseaudio: No object for name "alsa_output.usb-Kingston_HyperX_Cloud_II_Wireless_000000000001-00.analog-stereo"
Feb 23 10:27:23 PC-Linux kdeconnectd[1163]: org.kde.pulseaudio: No object for name "alsa_input.usb-MICE_MICROPHONE_USB_MICROPHONE_201308-00.mono-fallback"
Feb 23 10:27:23 PC-Linux kdeconnectd[1163]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Feb 23 10:27:23 PC-Linux kdeconnectd[1163]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Feb 23 10:27:23 PC-Linux kdeconnectd[1163]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Feb 23 10:27:23 PC-Linux kdeconnectd[1163]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Feb 23 10:27:23 PC-Linux kcminit[3157]: Initializing  "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Feb 23 10:27:23 PC-Linux kdeconnectd[1163]: org.kde.pulseaudio: No object for name "auto_null.monitor"
Feb 23 10:27:23 PC-Linux kcminit[3165]: Initializing  "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Feb 23 10:27:23 PC-Linux kcminit[3173]: Initializing  "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Feb 23 10:27:23 PC-Linux kcminit[3158]: Initializing  "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Feb 23 10:27:23 PC-Linux kwin_wayland[895]: kwin_core: Applying KScreen config failed!
Feb 23 10:27:23 PC-Linux plasmashell[1003]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-Kingston_HyperX_Cloud_II_Wireless_000000000001-00.analog-stereo"
Feb 23 10:27:23 PC-Linux plasmashell[1003]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-Kingston_HyperX_Cloud_II_Wireless_000000000001-00.analog-stereo"
Feb 23 10:27:23 PC-Linux plasmashell[1003]: org.kde.plasma.pulseaudio: No object for name "alsa_input.usb-MICE_MICROPHONE_USB_MICROPHONE_201308-00.mono-fallback"
Feb 23 10:27:23 PC-Linux plasmashell[1003]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-Kingston_HyperX_Cloud_II_Wireless_000000000001-00.analog-stereo"
Feb 23 10:27:23 PC-Linux plasmashell[1003]: org.kde.plasma.pulseaudio: No object for name "alsa_input.usb-MICE_MICROPHONE_USB_MICROPHONE_201308-00.mono-fallback"
Feb 23 10:27:23 PC-Linux plasmashell[1003]: org.kde.plasma.pulseaudio: No object for name "auto_null"
Feb 23 10:27:23 PC-Linux plasmashell[1003]: org.kde.plasma.pulseaudio: No object for name "auto_null.monitor"
Feb 23 10:27:23 PC-Linux plasmashell[1003]: org.kde.plasma.pulseaudio: No object for name "auto_null.monitor"
Feb 23 10:27:23 PC-Linux plasmashell[1003]: org.kde.plasma.pulseaudio: No object for name "auto_null.monitor"
Feb 23 10:27:23 PC-Linux kwin_wayland[895]: kwin_core: Applying KScreen config failed!
###### I waited ~30 seconds before switching back to tty1, during that time the log is full of "kwin_wayland[895]: kwin_core: Applying KScreen config failed!" ~15x per second
Feb 23 10:28:10 PC-Linux kwin_wayland[895]: kwin_core: Applying KScreen config failed!
Feb 23 10:28:10 PC-Linux kwin_wayland[895]: kwin_wayland_drm: Failed to create gamma blob! Invalid argument
Feb 23 10:28:10 PC-Linux kwin_wayland[895]: kwin_wayland_drm: Failed to create gamma blob! Invalid argument
Feb 23 10:28:10 PC-Linux kwin_wayland[895]: kwin_wayland_drm: Failed to create gamma blob! Invalid argument
Feb 23 10:28:11 PC-Linux wireplumber[821]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner
Feb 23 10:28:11 PC-Linux kdeconnectd[1163]: org.kde.pulseaudio: No object for name "auto_null"
Feb 23 10:28:11 PC-Linux plasmashell[1003]: org.kde.plasma.pulseaudio: No object for name "auto_null"
Feb 23 10:28:11 PC-Linux kdeconnectd[1163]: org.kde.pulseaudio: No object for name "auto_null.monitor"
Feb 23 10:28:11 PC-Linux plasmashell[1003]: org.kde.plasma.pulseaudio: No object for name "auto_null.monitor"
Feb 23 10:28:11 PC-Linux plasmashell[1003]: org.kde.plasma.pulseaudio: No object for name "@DEFAULT_SINK@"
Feb 23 10:28:11 PC-Linux plasmashell[1003]: org.kde.plasma.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Feb 23 10:28:11 PC-Linux kdeconnectd[1163]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Feb 23 10:28:11 PC-Linux kdeconnectd[1163]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Feb 23 10:28:11 PC-Linux wireplumber[821]: <WpPortalPermissionStorePlugin:0x5593314bcf80> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
Feb 23 10:28:11 PC-Linux plasmashell[1003]: org.kde.plasma.pulseaudio: No object for name "@DEFAULT_SINK@"
Feb 23 10:28:11 PC-Linux plasmashell[1003]: org.kde.plasma.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Feb 23 10:28:11 PC-Linux kdeconnectd[1163]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Feb 23 10:28:11 PC-Linux kdeconnectd[1163]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Feb 23 10:28:11 PC-Linux kdeconnectd[1163]: org.kde.pulseaudio: No object for name "alsa_output.usb-Kingston_HyperX_Cloud_II_Wireless_000000000001-00.analog-stereo"
Feb 23 10:28:11 PC-Linux kdeconnectd[1163]: org.kde.pulseaudio: No object for name "alsa_input.usb-Aukey-PC-LM1E_Camera_Aukey-PC-LM1E_Camera-02.analog-stereo"
Feb 23 10:28:11 PC-Linux kdeconnectd[1163]: org.kde.pulseaudio: No object for name "alsa_input.usb-Aukey-PC-LM1E_Camera_Aukey-PC-LM1E_Camera-02.analog-stereo"
Feb 23 10:28:11 PC-Linux plasmashell[1003]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-Kingston_HyperX_Cloud_II_Wireless_000000000001-00.analog-stereo"
Feb 23 10:28:11 PC-Linux plasmashell[1003]: org.kde.plasma.pulseaudio: No object for name "alsa_input.usb-Aukey-PC-LM1E_Camera_Aukey-PC-LM1E_Camera-02.analog-stereo"
Feb 23 10:28:11 PC-Linux plasmashell[1003]: org.kde.plasma.pulseaudio: No object for name "alsa_input.usb-Aukey-PC-LM1E_Camera_Aukey-PC-LM1E_Camera-02.analog-stereo"

Comment 3 Nate Graham 2023-02-27 19:15:14 UTC

Thanks for all that condensed and annotated info. It's really helpful. By any chance do the two DP monitors have the same serial number, or do both have a blank serial number? This can happen for screens from the same vendor.

Comment 4 hendrik.frueh 2023-02-28 14:38:43 UTC

(In reply to Nate Graham from comment #3)
> Thanks for all that condensed and annotated info. It's really helpful. By
> any chance do the two DP monitors have the same serial number, or do both
> have a blank serial number? This can happen for screens from the same vendor.

Unfortunately, no DP-1 is from Acer and DP-2 is from BenQ.
How would I go about checking for blank serial numbers?

Comment 5 hendrik.frueh 2023-02-28 16:30:03 UTC

I can also still reproduce it on 5.27.2

Comment 6 Nate Graham 2023-02-28 19:28:53 UTC

Oh good, if they're from different companies, there's a better chance! You can run `kscreen-console bug` in a terminal window and look in the EDID sections. Can you paste them here, one for each monitor?

Comment 7 hendrik.frueh 2023-03-01 10:03:07 UTC

(In reply to Nate Graham from comment #6)
> Oh good, if they're from different companies, there's a better chance! You
> can run `kscreen-console bug` in a terminal window and look in the EDID
> sections. Can you paste them here, one for each monitor?

Sure!
HDMI-A-1 EDID Info: 
        Device ID:  "xrandr-AAA"
        Name:  "AAA"
        Vendor:  ""
        Serial:  ""
        EISA ID:  ""
        Hash:  "c9a972edd32753ee754fa09a6d8cb57f"
        Width:  0
        Height:  0
        Gamma:  1
        Red:  QQuaternion(scalar:1, vector:(0.635742, 0.347656, 0))
        Green:  QQuaternion(scalar:1, vector:(0.290039, 0.588867, 0))
        Blue:  QQuaternion(scalar:1, vector:(0.142578, 0.0800781, 0))
        White:  QQuaternion(scalar:1, vector:(0.313477, 0.329102, 0))

DP-1 EDID Info: 
        Device ID:  "xrandr-Acer Technologies-VG270U P-2221937607"
        Name:  "VG270U P"
        Vendor:  "Acer Technologies"
        Serial:  "2221937607"
        EISA ID:  ""
        Hash:  "006a260335e60ba1f428d2c7d3f32e40"
        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))

DP-2 EDID Info: 
        Device ID:  "xrandr-Acer Technologies-VG270U P-2221937607"
        Name:  "VG270U P"
        Vendor:  "Acer Technologies"
        Serial:  "2221937607"
        EISA ID:  ""
        Hash:  "006a260335e60ba1f428d2c7d3f32e40"
        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))


The reason my HDMI monitor doesn't have a serial number is probably because I salvaged the panel and bought a controller board for it on eBay, but it also is the only one of them which keeps its priority. Apart from that, I apparently have 5 kscreen configs, which seems odd since this is a desktop and I don't randomly connect new monitors or smth like that.

Comment 8 Nate Graham 2023-03-01 15:34:00 UTC

Ok, so you're hitting the issue because two of your screens have the same serial numbers and therefore identical hash values. That makes it the same issue as Bug 452614 which is in the process of being fixed.

*** This bug has been marked as a duplicate of bug 452614 ***