Bug 469152

Summary: primary display changes randomly & tick box doesn't represent the actual primary display
Product: [Applications] systemsettings Reporter: paul2meyer
Component: kcm_kscreenAssignee: kscreen-bugs-null <kscreen-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: major CC: nate, plasma-bugs
Priority: NOR    
Version: 5.27.4   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: xrandr shows the actual primary display and the gui shows the wrong one

Description paul2meyer 2023-04-29 18:29:24 UTC
Created attachment 158540 [details]
xrandr shows the actual primary display and the gui shows the wrong one

Selecting the primary display in the display configuration section of system settings doesn't function properly.
If you set a monitor as primary , it will change at seemingly random times and often at reboot. 
It doesn't indicate the change in any way however. The tick box for being primary is still checked on the monitor that no longer is the primary monitor. You can only see it if you look up what monitor is the primary display with xrandr.
In order to fix it without using the terminal you have to set a secondary monitor as primary and then change it back.

This causes games and other fullscreen applications to launch on the wrong monitor. 

STEPS TO REPRODUCE
1. Set a display as primary within the display configuration page
2. Wait an inconsistent amount of time

OBSERVED RESULT
The primary monitor changes to secondary display without any indication.

EXPECTED RESULT
The primary monitor stays the same / the tick box should indicate what monitor is actually the primary one.

SOFTWARE/OS VERSIONS
Distro: Arch Linux
Kernel: 6.1.26
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION
This issue is very frustrating because there isn't any obvious indication of anything being wrong. 
It is only when full screen applications like games launch that you notice the issue.
Comment 1 Nate Graham 2023-05-02 16:07:40 UTC

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