https://bugs.kde.org/show_bug.cgi?id=517499
--- Comment #11 from Marco Martin <[email protected]> --- (In reply to Branislav Klocok from comment #0) > kscreen-doctor -o shows DP-4 as priority 1 (correct) > KWin maps Screen 0 = eDP-1, Screen 1 = DP-4 if kscreen-doctor -o shows DP-4 as priority 1, then kwin maps screen 0 as DP-4, ignore the [ScreenConnectors] config group, is not used anymore, we should have put some code that cleaned it programmatically to not generate confusion but sadly we didn't, sorry. > Panel/taskbar appears on eDP-1 (Screen 0) despite DP-4 having priority 1 > Setting the primary again in System Settings fixes it until the next > location change You mostly switch between two locations or every time is a completely new set of screens? Here is how the system is supposed to work (not saying is the best possible/ correct way, but is the behavior it was designed) * the only source of truth for the order of screens is kwin. plasma, kscreen-doctor and the kcm ask kwin for the topology or ask for changes * every new set of screens is treated as a new completely independent setup * when going back to a "known" set of screen, the order that was associated with it is restored For instance i mostly alternate my laptop from a setup with a dock that has the usual external monitor/mouse/keyboard, and in that case the primary screen is always the external one (and it remembers it every time i connect it) and another setup where it's attached to a projector, and in tat case the primary screen is always the internal one, and it remembers this as well. Now, in your case, if every time you get back to a known setup, like an external monitor at home and does not remember that the primary screen is the external one, that would be where the bug is. in appletsrc is important that your panel (and the proper desktop containment you want in the external screen in your case) always has lastScreen=0, which means to stay in the screen considered primary by kwin. This would tell that the plasmashell part is correct > Investigation revealed two issues: > 1. Stale ScreenConnectors mapping in plasmashellrc yeah, that should be ignored, has no effect > 2. plasma-kscreen.service not saving profiles > The plasma-kscreen.service was found inactive (dead), and even after the kscreen service is supposed to be active only on x11, on wayland its job is taken over by kwin (which reads the configs in ~/.local/share/kscreen/ ). > starting it, no profile files are written to ~/.local/share/kscreen/ when > changing display settings via kscreen-doctor or System Settings. The > OutputRetention=1 setting in kscreenrc does not help. This means display > preferences cannot persist per-arrangement. Ugh, Here seems to be the actual issue. unfortunately i don't seem to be able to reproduce (even on a 6.6 setup) -- You are receiving this mail because: You are watching all bug changes.
