I have noticed that several kwin window rules, that force an initial size of a window do have no effect anymore. I have also tried to force "ignore requested geometry" to yes, but with no effect. I can reproduce this behavior for kate and okular, but it works with nfoviewer (gtk). SOFTWARE/OS VERSIONS KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52 Qt Version: 5.11.2
Please provide xprop and xwininfo for an affected application and also add the rule for it.
Created attachment 116345 [details] kwinrulesrc (see kate rule)
Created attachment 116346 [details] kate xprop output
Created attachment 116347 [details] kate xwininfo output
I have notice, that the windows always start maximized. Even, if I have closed them in an unmaximized state before. On another computer, the kwin rules and the maximization state works correctly. Thus, i was wandering, what might be the difference. One thing, that came into my mind was, that I had installed a tilling kwin scrip before on the broken system, but uninstalled it, since it was not working propertly. Maybe that script left something flying around?
installed scripts were: https://store.kde.org/p/1187647 https://store.kde.org/p/1112554
you could check in ~/.config/katerc in section [MainWindow] whether it tries to start in maximized state. For a test you could remove katerc.
(In reply to Martin Flöser from comment #7) > you could check in ~/.config/katerc in section [MainWindow] whether it tries > to start in maximized state. For a test you could remove katerc. That was indeed the case. After removing katerc completely, it does not start maximized anymore. However, it still does not respect the window rule.
Created attachment 116352 [details] kate xprop output with deleted katerc
Created attachment 116353 [details] kate xwininfo output with deleted katerc
I added a similar rule for kate to my system and the geometry was also not applied. I'll add this to our window rules test set, so that we can either figure out whether it's a problem on the client or kwin side.
Just created the test case and it passes.
After further testing I conclude that my kate also reacts properly on the size rule I create.
could you please provide the output of: qdbus org.kde.KWin /KWin supportInformation
Created attachment 116441 [details] kwin support information sorry i was a bit late, since the affected computer is only accessible (Wednesday to Friday to me)
I can only conclude that this must be a change in Qt.
(In reply to Martin Flöser from comment #16) > I can only conclude that this must be a change in Qt. I have another system with identical qt version, where the rule works as expected (I copied the config from kwinrulesrc, thus is should be identical)
What is different in the systems?
They both run the same stack of kde software and xorg-server. Thus, this might be some "old config flying around" problem...
I have exactly the same problem with multiple applications (Dolphin, KMail, and I'm sure others). Windows always start maximized no matter which window rules or sizes you had set, EXCEPT if I use "Force". THEN it works, but obviously it's now non-resizable, which is a problem. Operating System: KDE neon 5.17 KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 5.0.0-31-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-2430M CPU @ 2.40GHz Memory: 3.8 GiB of RAM
If it helps: It seems like window rules will be working, and as soon as ANOTHER window rule is added, ALL rules suddenly stop working, at least their "size" parts ("No borders" for example continues to work for ALL rules). Very strange. (all "size" related rules stopped working for me when I added an additional rule for Discover.)
I cannot reproduce this when forcing "ignore requested geometry" to yes. Without this setting, the application can override the initial size property by setting a different geometry. Is this still happening to you?
Created attachment 134604 [details] screenshot of okular settings It works for kate in my case, but still fails for okular. Operating System: Gentoo Linux KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.9.14-gentoo OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 30.9 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000
Since Ismael reported that the rule misfunction might be related to other rules, if have tested if the rule ordering has an effect. Result: Geometry is not applied, regardless if the rule is placed first and last in the rule list.
Created attachment 134606 [details] problematic okularrc removing the okularrc file did resolve the issue for me. Thus, this might be an Okular issue not requesting a certain geometry, but setting it manually after start. I have attached the problematic okularrc file (with removed recent files)
I'm not sure if this is related, but I remember that I had the general problem that KDE applications would randomly revert to launching maximized, no matter how many window rules I defined for them. I fixed it by running the following script one a minute from Cron: cd /home/intrr/.config sed -i 's/^Window-Maximized.*true//' konsolerc dolphinrc systemsettingsrc okularrc gwenviewrc kolourpaintrc kwriterc kdialogrc
(In reply to Alexander Ewering from comment #26) > I'm not sure if this is related, but I remember that I had the general > problem that KDE applications would randomly revert to launching maximized, > no matter how many window rules I defined for them. > > I fixed it by running the following script one a minute from Cron: > > cd /home/intrr/.config > sed -i 's/^Window-Maximized.*true//' konsolerc dolphinrc systemsettingsrc > okularrc gwenviewrc kolourpaintrc kwriterc kdialogrc that analysis would fit my case
(In reply to Till Schäfer from comment #27) > (In reply to Alexander Ewering from comment #26) > > I'm not sure if this is related, but I remember that I had the general > > problem that KDE applications would randomly revert to launching maximized, > > no matter how many window rules I defined for them. > > > > I fixed it by running the following script one a minute from Cron: > > > > cd /home/intrr/.config > > sed -i 's/^Window-Maximized.*true//' konsolerc dolphinrc systemsettingsrc > > okularrc gwenviewrc kolourpaintrc kwriterc kdialogrc > > that analysis would fit my case Okay... so this is odd then. Of course, user-defined window rules should always have priority over anything the app itself decides. I know, I'm probably missing technical details (sorry!), but yeah... in essence, that should be the outcome. From what I understand, some apps change the window size very quickly after launch, but unfortunately also AFTER the "Apply initially" rules have been applied. So, a classical race condition then.
> From what I understand, some apps change the window > size very quickly after launch, but unfortunately also AFTER the "Apply > initially" rules have been applied. So, a classical race condition then. That is right. All those applications are remembering their own geometry/state and trying to set it at launch, but after kwin has applied the `Apply Initially` rules. To overcome this, there's the setting `Ignore requested geometry`, which makes kwin to ignore size and position requests from the app. As I understand from the comments, it's just only `Window-Maximized=true` the remaining issue. Is that right? If in general you don't want any KDE apps to remember their last position (and set it back when re-lauched), you can disable this behavior in `Window Behavior->Advanced->Allow apps to remember the position ...` You can also override this for specific ones setting the rule properties "Vertically Maximized" and "Horizontally Maximized", both to `Apply Initially: No`.
Reading again through this report, I think that the original problem is indeed resolved (kate did not act on rules despite deleting katerc in the beginning). Should I open another bug report, that matches the current behavior more closely? I still think there are some problems remaining here. a) okular always starts in maximized state even if it was closed in unmaximized state. Thus, it remembered the maximization in the first place, but not the demaximization ... b) "Ignore requested geometry" does not help. See screenshot of okular settings (I have already forced it). Does this ignore setting include the maximized state? I still think, that apply initially rules should always work with this setting forced. At least the description of the feature should be a little bit more clear about the affected rules (size, position, maximized?). Currently the description only mentions position, but I think it will at least affect size, too.
Thanks a lot for summarizing up! > Should I open another bug report, that matches the current behavior more > closely? I still think there are some problems remaining here. Yes, I think there's more chances to get the remaining issues solved by filling two focused bug reports, especially if one of them only affects okular. > a) okular always starts in maximized state even if it was closed in > unmaximized state. Thus, it remembered the maximization in the first place, > but not the demaximization ... I cannot reproduce this, so there must be some other differences in our setups (multi-screen?) and/or okular internals. Filling a bug against it can help figuring out the problem. > b) "Ignore requested geometry" does not help. See screenshot of okular > settings (I have already forced it). Does this ignore setting include the > maximized state? I still think, that apply initially rules should always > work with this setting forced. At least the description of the feature > should be a little bit more clear about the affected rules (size, position, > maximized?). Currently the description only mentions position, but I think > it will at least affect size, too. This is a very good point. I would also assume that the geometry also affects maximize state, but it in fact doesn't. It is worth looking for a possible solution, or at least disambiguate it as you propose.
If you don't mind I'll be closing this, as the initial issue doesn't seem to reproduce in those terms, and you already submitted follow-up bugs. For reference: * Window rule "Ignore requested geometry" has unclear effect: bug#431265 * Okular always starts in maximized state: bug#431267 Thanks!