https://bugs.kde.org/show_bug.cgi?id=527437

--- Comment #1 from [email protected] ---
Cause found: a stray rule group in ~/.config/kwinrulesrc that 6.8 now loads.

[64e934d6-5efb-4947-ba06-b4b6394dd723]
screen=2
screenrule=2

[General]
rules=

The group has no match properties, so it force-applies screen 2 to every
window. 6.7 ignored it because it wasn't listed in rules=. Since d138c933d9,
RuleBookSettings::usrRead() only purges unlisted groups when the rules list is
non-empty. Mine was empty, so the orphan was added to Order instead and became
active.

Since 4ba4a99645, screen=2 means the priority 3 output. That's why windows
ended up there, and why the bug goes away with two outputs (index out of
range).

Deleting the group and running "qdbus6 org.kde.KWin /KWin reconfigure" fixed
it.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to