[kwin] [Bug 401103] Rule "Apply Initially" on size does not work anymore for several KDE applications

2021-01-07 Thread Ismael Asensio
https://bugs.kde.org/show_bug.cgi?id=401103

Ismael Asensio  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #32 from Ismael Asensio  ---
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!

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

[kwin] [Bug 401103] Rule "Apply Initially" on size does not work anymore for several KDE applications

2021-01-07 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=401103

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[kwin] [Bug 401103] Rule "Apply Initially" on size does not work anymore for several KDE applications

2021-01-07 Thread Ismael Asensio
https://bugs.kde.org/show_bug.cgi?id=401103

--- Comment #31 from Ismael Asensio  ---
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.

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

[kwin] [Bug 401103] Rule "Apply Initially" on size does not work anymore for several KDE applications

2021-01-07 Thread Till Schäfer
https://bugs.kde.org/show_bug.cgi?id=401103

--- Comment #30 from Till Schäfer  ---
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.

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

[kwin] [Bug 401103] Rule "Apply Initially" on size does not work anymore for several KDE applications

2021-01-06 Thread Ismael Asensio
https://bugs.kde.org/show_bug.cgi?id=401103

--- Comment #29 from Ismael Asensio  ---
> 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`.

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

[kwin] [Bug 401103] Rule "Apply Initially" on size does not work anymore for several KDE applications

2021-01-06 Thread Alexander Ewering
https://bugs.kde.org/show_bug.cgi?id=401103

--- Comment #28 from Alexander Ewering  ---
(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.

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

[kwin] [Bug 401103] Rule "Apply Initially" on size does not work anymore for several KDE applications

2021-01-06 Thread Till Schäfer
https://bugs.kde.org/show_bug.cgi?id=401103

--- Comment #27 from Till Schäfer  ---
(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

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

[kwin] [Bug 401103] Rule "Apply Initially" on size does not work anymore for several KDE applications

2021-01-06 Thread Alexander Ewering
https://bugs.kde.org/show_bug.cgi?id=401103

--- Comment #26 from Alexander Ewering  ---
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

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

[kwin] [Bug 401103] Rule "Apply Initially" on size does not work anymore for several KDE applications

2021-01-06 Thread Till Schäfer
https://bugs.kde.org/show_bug.cgi?id=401103

Till Schäfer  changed:

   What|Removed |Added

Version|5.14.3  |5.20.4

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

[kwin] [Bug 401103] Rule "Apply Initially" on size does not work anymore for several KDE applications

2021-01-06 Thread Till Schäfer
https://bugs.kde.org/show_bug.cgi?id=401103

--- Comment #25 from Till Schäfer  ---
Created attachment 134606
  --> https://bugs.kde.org/attachment.cgi?id=134606&action=edit
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)

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

[kwin] [Bug 401103] Rule "Apply Initially" on size does not work anymore for several KDE applications

2021-01-06 Thread Till Schäfer
https://bugs.kde.org/show_bug.cgi?id=401103

--- Comment #23 from Till Schäfer  ---
Created attachment 134604
  --> https://bugs.kde.org/attachment.cgi?id=134604&action=edit
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

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

[kwin] [Bug 401103] Rule "Apply Initially" on size does not work anymore for several KDE applications

2021-01-06 Thread Till Schäfer
https://bugs.kde.org/show_bug.cgi?id=401103

Till Schäfer  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #24 from Till Schäfer  ---
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.

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

[kwin] [Bug 401103] Rule "Apply Initially" on size does not work anymore for several KDE applications

2021-01-04 Thread Ismael Asensio
https://bugs.kde.org/show_bug.cgi?id=401103

Ismael Asensio  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REPORTED|NEEDSINFO
 CC||isma...@gmail.com

--- Comment #22 from Ismael Asensio  ---
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?

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

[kwin] [Bug 401103] Rule "Apply Initially" on size does not work anymore for several KDE applications

2019-10-20 Thread Alexander Ewering
https://bugs.kde.org/show_bug.cgi?id=401103

--- Comment #21 from Alexander Ewering  ---
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.)

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

[kwin] [Bug 401103] Rule "Apply Initially" on size does not work anymore for several KDE applications

2019-10-20 Thread Alexander Ewering
https://bugs.kde.org/show_bug.cgi?id=401103

Alexander Ewering  changed:

   What|Removed |Added

 CC||ae@seven.systems

--- Comment #20 from Alexander Ewering  ---
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

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

[kwin] [Bug 401103] Rule "Apply Initially" on size does not work anymore for several KDE applications

2018-11-23 Thread Till Schäfer
https://bugs.kde.org/show_bug.cgi?id=401103

--- Comment #19 from Till Schäfer  ---
They both run the same stack of kde software and xorg-server. Thus, this might
be some "old config flying around" problem...

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

[kwin] [Bug 401103] Rule "Apply Initially" on size does not work anymore for several KDE applications

2018-11-22 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=401103

--- Comment #18 from Martin Flöser  ---
What is different in the systems?

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

[kwin] [Bug 401103] Rule "Apply Initially" on size does not work anymore for several KDE applications

2018-11-22 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=401103

Christoph Feck  changed:

   What|Removed |Added

Summary|KWin (5.14.3) Rule "Apply   |Rule "Apply Initially" on
   |Initially" on size does not |size does not work anymore
   |work anymore for several|for several KDE
   |KDE applications|applications

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