https://bugs.kde.org/show_bug.cgi?id=517499
--- Comment #18 from Aaron Tinio <[email protected]> --- Small update from my AMD/Arch setup in comment 7. On Plasma Workspace 6.7.4 and KWin 6.7.4, my current docked, lid-open state has the same duplicate minimum priority reported in comment 17: DP-2 enabled, connected, priority 1 eDP-1 enabled, connected, priority 1 KWin has also persisted that tie in kwinoutputconfig.json. Plasma's screen ordering is currently internal screen 0 and external screen 1. This is only a startup baseline, not a capture of the transition that introduced the tie: my local workaround had already moved the panel to the external display. So I cannot attribute the tie to a particular DRM, brightness, lid, or KWin-config event yet. I have replaced my earlier recorder with one that captures correlated immediate, settled, and delayed state around DRM, brightness, and kwinoutputconfig.json events. It records the live KScreen priorities, Plasma screen/panel mapping, projected saved topology, config mtime/hash, DRM connectors, and lid state, while excluding EDIDs and output UUIDs. It does not rewrite KWin priorities, and on a tie it only uses my explicit local DP preference for panel recovery. I'll attach the next captured transition that creates or clears the tie. -- You are receiving this mail because: You are watching all bug changes.
