https://bugs.kde.org/show_bug.cgi?id=421055
Bug ID: 421055 Summary: [kcm/kwinrules X11] Window sizing rules broken since a04b40dad: KWinRules KCM Redesign Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: 1i5t5.dun...@cox.net Target Milestone: --- Since the window rules kcm redesign in ao4b40dad (or my first update after that anyway, pretty close), none of the normal-mode window sizing rules, size, minimum size, maximum size, seem to work at all, in X at least. (Other geometry-related rules such as position and maximize-horizontally/vertically continue to work just fine.) I have dual 75-inch/1.9m 4K TVs as monitors so have a /lot/ of screen real estate. In normal operations I'll run a fullscreen youtube or the like on one monitor, while my normal work goes on the other one. I've standardized most of my normal working apps, firefox (when not full-screened), often multiple konsole windows, claws for mail and feeds, pan for news (nntp), kpat and ksudoku for games, and an always-open ksysguard in the corner, to 1280x1080, thus letting me tile my working windows in a 3x2=6 grid across the "working" monitor, with the 1280x1080 sizes enforced as necessary by appropriate window rules. Only now none of that size enforcement is working and it's playing havoc with my grid setup. =:^( There's a potential hint at the problem in that loading up existing window rules in the new kcm, the size rules are there, but with the sizes all zeroed out. If I hit detect, the values fill in, but hit apply (with no actual window sizes changing if they were changed), leave the ruleset and come back to it, and the values are zeroed out again. Further, checking the kwinrulesrc file, the size values for anything I've changed in the kcm are apparently reset to defaults, 0 for size and min/max values for those, 1 for min, 32767 for max, and the zeroed-out sizes are apparently deleted/not-stored. Some of the ones I've not changed remain as they were in kwinrulesrc, but a couple, firefox and claws in particular as those are where I noticed the rules misbehaving and went to check-on/adjust, are screwed up. So it appears the default values are overriding the actually set values once the individual window ruleset is loaded into the kcm, and that gets written back to the kwinrulesrc file. Something also triggered the window rulesets for claws and firefox to misbehave causing me to visit their rulesets in the kcm in the first place, as well, but I'm not sure if that was kwin's fault or not, while I do know that once a change is made in the kcm, the sizes get broken, and that it was working before the kcm redesign. kde-frameworks and kde-plasma are git master. Current qt is 5.15.0-beta4. xorg-server-1.20.8, mesa-20.0.6, xf86-video-amdgpu, kernel 5.7-rcs (but 5.6.0 does it too). Current kwin was updated with today's update, to d5e5e2f1c, after which I did the usual quit X/plasma, restart updated services, remount root ro again, and restart X/plasma, dance. -- You are receiving this mail because: You are watching all bug changes.