https://bugs.kde.org/show_bug.cgi?id=507916
--- Comment #19 from Ismael Asensio <[email protected]> --- > If the rules work when creating them from the UI, but not from scratch with > the exact same text,that would be a bug. That would be kinda impossible technically :) In general I'd advise against touching the file manually except for debugging purposes (as is the case here), because there are some automatic things the UI does that need to be replicated: - To take place, the rule ID (the config group name) needs to be added to list in the `rules` property (in the `[General]` section) and will be processed in that order. - KWin needs to gets triggered to re-process the file when a rule changes, what the UI does. This can be done manually from the command line `qdbus org.kde.KWin /KWin org.kde.KWin.reconfigure`. Trying to follow up the sequence, I think there is not a bug here but a mismatched config file or more of an unexpected result? I'll try to explain what I got. Please, tell me if I missed/misunderstood something. The original rule would not work at all (any properties), because it wouldn't match. The `wmclass` property is quite weird because it means two different things depending on whether `wmclasscomplete` is selected. When that is `false` (or not in the file as it is the default) it needs just the first string of the "app" (just the first `vncviewer` in this case), so having two strings will make the match fail. This is a bit of an X11-ism, which we might improve in the future maybe. The second rule ID (`326c0f64-`) doesn't appear on the UI list, so what's written there will not affect the results and can be removed safely. I see a lot of other config groups and keys that shouldn't be there. I don't know what might have caused that, but should be harmless. I'd recommend to remove them in any case, those are the properties that end in [$d] -- You are receiving this mail because: You are watching all bug changes.
