• Kmail2 - Configure Special Window Setting: does not register (sid)

    From inkbottle@21:1/5 to All on Sat Jan 16 17:30:01 2021
    Since I was upset with Kmail always opening in fullscreen, I decided to let go of fixing things, and instead force it to do what I want through `Alt f3` "configure special window settings".

    So I just do that, and click OK, in the dialog, and then the screen flashes as it usually do in that specific situation, and then the "settings" window is gone, just as it does nowadays, and then I go in "settings" and "windows rules", in order to set the specific parameters I want it to assume, and then:

    dah-dah! Nothing. Nothing it registered at the name "Kmail", or "Kmail2" as
    the dialog called it.

    I already have four of them, three of them long standing, and one newly created, for firefox, which was stubbornly opening in very small window, and that I had to tame (as a matter of fact it started behaving like a bad application a few week ago too).
    Anyway, I usually know how it works.

    The long standing are emacs konsole and okular and are of the "application" persuasion.

    The new one is of "window settings" sort.

    Anyway, following these directions, it doesn't work, doesn't do anything; but it duly flashes the screen, showing it did do some real work in the configure window setting line.

    Weird.

    I tell you if I have more data.
    Chris

    PS: I did `rm -rf ~/.kde4`, in order to remove all easy and safe to remove settings and config things, as I've been recently suggested to do, some times before the above thing.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From inkbottle@21:1/5 to All on Sun Jan 24 18:40:02 2021
    On Saturday, January 16, 2021 5:26:18 PM CET you wrote:
    Since I was upset with Kmail always opening in fullscreen, I decided to let go of fixing things, and instead force it to do what I want through `Alt
    f3` "configure special window settings".

    So I just do that, and click OK, in the dialog, and then the screen flashes as it usually do in that specific situation, and then the "settings" window is gone, just as it does nowadays, and then I go in "settings" and "windows rules", in order to set the specific parameters I want it to assume, and then:

    dah-dah! Nothing. Nothing it registered at the name "Kmail", or "Kmail2" as the dialog called it.

    I already have four of them, three of them long standing, and one newly created, for firefox, which was stubbornly opening in very small window, and that I had to tame (as a matter of fact it started behaving like a bad application a few week ago too).
    Anyway, I usually know how it works.

    The long standing are emacs konsole and okular and are of the "application" persuasion.

    The new one is of "window settings" sort.

    Anyway, following these directions, it doesn't work, doesn't do anything;
    but it duly flashes the screen, showing it did do some real work in the configure window setting line.

    Weird.

    I tell you if I have more data.
    Chris

    PS: I did `rm -rf ~/.kde4`, in order to remove all easy and safe to remove settings and config things, as I've been recently suggested to do, some
    times before the above thing.

    So as I said, Alt-F3 on kmail, and special windows setting, does not register nothing.

    Now, since the constant opening of kmail2 in full screen mode is quite a pita, I went in system settings and created the rule from there, and then did the action taking a snapshot of the windows properties, and then selected "force" for the window size.

    That sequence of action has just no effect at all.

    Really it just seems as though, kmail2 is using another window manager altogether.

    Is it?

    Like it is using old components and is not integrating well with kwin?

    ---

    I've just dist-upgraded, and tried everything again.

    Alt-f3 > special window setting does not register rules for kmail,
    Neither does special application settings

    And if trying to force things by going to configure window manager and crating an entry there. Well the entry is created but has no effect.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sandro =?ISO-8859-1?Q?Knau=DF?=@21:1/5 to All on Wed Jan 27 17:57:23 2021
    Hey,

    Now, since the constant opening of kmail2 in full screen mode is quite a pita, I went in system settings and created the rule from there, and then
    did the action taking a snapshot of the windows properties, and then
    selected "force" for the window size.

    That sequence of action has just no effect at all.

    Really it just seems as though, kmail2 is using another window manager altogether.

    Is it?

    Like it is using old components and is not integrating well with kwin?

    the special window settings are only inside kwin and have nothing to do with the application you configure. That's why you can also modify GTK applications or tk applications. But on the other side there is this state storage of the windows, that may interfere in here. Have a look inside ~/.config/kmail2rc there you see this State keys, that represent the geometric representation of the windows. I would suggest to delete those keys from kmail2rc, when kmail is not running.

    hefee
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEOewRoCAWtykmSRoG462wCFBgVjYFAmARm3MACgkQ462wCFBg VjbROQ/9EGEJvz9jz4basqy5YMsYvHl6XO9ngdzWsIXgCDIwi6QBqI7kHVwhVwSN 4rF8ttvkIRMZTrlUlScTc5V9u34vOfq/3f1uOqP7GTNSNYpbFoXGktrSK7rnGT5W UU7WGnZfrQTHcIBem7TXRn4kUYXHSPGMalr/Ay9S/WNt7Xa+Et55iBxOzP3nfxgK kmBgVjJJxoSdlJgURvxU/loj2abHrgtFy9TLn9Q9p+DL5rBZQozUQSRcvqihIMbP dTSrueTgYbBrEMvvnlRdRYqEI7jmKPTG/lSS9OwcJMqH8SDCSY8o/+pQQEgOtOot L0NP9MKiDm1qws4WK2zS8pd8wJVHsHpHbqr9UTa/VoP9h2lhR70mC76zU4CKDv+J jvGlVBMWrdMGkXb9MnrURGZeAcsEqTl+MaCivEJgxcjog+fI9lIYQBMILbgFb7hB SSd3cEuYT7vajdA6l4GX3mMGD55jZu5Vkov5jixK3uMVoPo5JwkVvQ5GMk9+kcxM 0oXdsGeBvcG7QXXadsf7bokjYiAK+kBgYLaY6cbEi74u6rR7vJPqEWoGS/7Jw9C5 w9cc7MJsVwHpIb4eopQeAaKYigtPFofFhokQDYukdFe+eS8KVdAwOMr/0Sl7vAiu /74g2HeQb0WiWTGm13YYEGG4if/TiwaZ3naqLJ5KsMNHwh+xyC8=
    =j268
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From inkbottle@21:1/5 to All on Thu Jan 28 00:00:03 2021
    On Wednesday, January 27, 2021 5:57:23 PM CET Sandro Knauß wrote:
    Hey,

    Now, since the constant opening of kmail2 in full screen mode is quite a pita, I went in system settings and created the rule from there, and then did the action taking a snapshot of the windows properties, and then selected "force" for the window size.

    That sequence of action has just no effect at all.

    Really it just seems as though, kmail2 is using another window manager altogether.

    Is it?

    Like it is using old components and is not integrating well with kwin?

    the special window settings are only inside kwin and have nothing to do with the application you configure. That's why you can also modify GTK applications or tk applications. But on the other side there is this state storage of the windows, that may interfere in here. Have a look inside ~/.config/kmail2rc there you see this State keys, that represent the geometric representation of the windows. I would suggest to delete those
    keys from kmail2rc, when kmail is not running.

    Thanks a lot for the suggestion, doing that asap.


    hefee

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sandro =?ISO-8859-1?Q?Knau=DF?=@21:1/5 to All on Sat Feb 6 11:24:33 2021
    Hey,

    in the weekly news from KDE[1] I stumbled over:
    KDE apps which where closed while maximized now always re-open maximized, and if they were later un-maximized and closed, they will re-open un-maximized (Nate Graham, Frameworks 5.79)

    That sounds really like the your detected issue. Okay than the issue is, that write and read code are not synchronised ;)

    hefee


    [1] https://pointieststick.com/2021/02/05/this-week-in-kde-kwin-gains-direct-scan-out-and-gwenview-gets-a-lot-of-love/
    [2] https://bugs.kde.org/430521

    --

    On Mittwoch, 27. Januar 2021 23:56:46 CET inkbottle wrote:
    On Wednesday, January 27, 2021 5:57:23 PM CET Sandro Knauß wrote:
    Hey,

    Now, since the constant opening of kmail2 in full screen mode is quite a pita, I went in system settings and created the rule from there, and
    then
    did the action taking a snapshot of the windows properties, and then selected "force" for the window size.

    That sequence of action has just no effect at all.

    Really it just seems as though, kmail2 is using another window manager altogether.

    Is it?

    Like it is using old components and is not integrating well with kwin?

    the special window settings are only inside kwin and have nothing to do with the application you configure. That's why you can also modify GTK applications or tk applications. But on the other side there is this state storage of the windows, that may interfere in here. Have a look inside ~/.config/kmail2rc there you see this State keys, that represent the geometric representation of the windows. I would suggest to delete those keys from kmail2rc, when kmail is not running.

    Thanks a lot for the suggestion, doing that asap.

    hefee


    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEOewRoCAWtykmSRoG462wCFBgVjYFAmAebmEACgkQ462wCFBg VjaInQ//fbPeloG5TmWkwhJ9eud1EUIxMLmXqlBSCrAoQAUR8FbXf17xNAFf6/TD rI1e5uwMYe332tzNG0UlcDKLpL237GZCp2LBL7hVf8Q3cmLYrLzmMKilfLPLsWu1 lU4hqhgDFDVwlCWu5uVmh6N7DQ1XiGGSGi9cLExzFUhcbV6PAA2ILbtwCsXEsiSH VkIfHuvkoGBQ8xdI39KQzwqvlfGFdoZKnQy4kyL8yCVWXl7FnN5zySZjUgUTY8PO W9SfL4LmBZo/PUdLvKHJXe6XsZN6X/l0dYKGYc8I8/EKukq3fXG2HMGpIO00lwNo iBaPznH/O1Sa8af1+goHW8GJDzJzUqvmH9W2vq6uDlM1d0fu9SbT9d8a6DFIR02d GuRE76QIdfRU66XhJZJkMyQ6fCdF2uAsbHdlZzvsuo74po1CtdbX9XMt6VfHGKL2 VqUdPW/2ASQZm1iqTGu6PVyLi1VSGs4xZXwDHX9vlN7ChUjzEgVEB8QajeghaWrE mfBMpEektx+mSICP4IDVgq5txVlnB0p5mx7MLbl5LZ+rtXH+RooFRPp6z5UdHklZ XqliH4QUHQJ5nViACN1rLsmgHI7rEAwvknKftnzvfHT+h38+Sm84phk3NuyJSHww 6BkrNe6kVSJ3iUoYuOVgJ6w9Ny1vtUBuyPam43CxpGK2AEOaGo4=
    =th7b
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?ISO-8859-1?Q?Aur=E9lien?= COUDERC@21:1/5 to All on Wed Feb 10 21:40:02 2021
    Le samedi 6 février 2021, 13:28:11 CET Sandro Knauß a écrit :
    Hey Norbert,

    Should we cherry-pick the relevant fix commit https://invent.kde.org/frameworks/kconfig/commit/b57c7ad9acf45928a6debefcd 43 2cc50432fefdb

    Yes we should cherry-pick this one.

    For the record, this has been uploaded as part of kconfig 5.78.0-4, thanks for the suggestion and thanks Norbert for the cherry-pick.


    Happy hacking !
    --
    Aurélien

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Norbert Preining@21:1/5 to All on Sat Feb 6 11:50:02 2021
    Hi Sandro,

    great find!

    [2] https://bugs.kde.org/430521

    Should we cherry-pick the relevant fix commit https://invent.kde.org/frameworks/kconfig/commit/b57c7ad9acf45928a6debefcd432cc50432fefdb

    Sounds like a useful addition...

    WDYT?

    Norbert

    --
    PREINING Norbert https://www.preining.info
    Fujitsu Research Labs + IFMGA Guide + TU Wien + TeX Live + Debian Dev
    GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sandro =?ISO-8859-1?Q?Knau=DF?=@21:1/5 to Norbert Preining on Sat Feb 6 13:28:11 2021
    Copy: debian-kde@lists.debian.org

    Hey Norbert,

    Should we cherry-pick the relevant fix commit https://invent.kde.org/frameworks/kconfig/commit/b57c7ad9acf45928a6debefcd43 2cc50432fefdb

    Yes we should cherry-pick this one.

    hefee
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEOewRoCAWtykmSRoG462wCFBgVjYFAmAei1sACgkQ462wCFBg VjYdFxAArplffp1GHELTnF4XX1UrR3JCikxSjHELRqR11xHj6N4H/2RJPzdQTSVb u54j3k3v4+WVqHLPGnwLTxH3VOm3n1MkTIpnYhGi9bOVJD6PezLch4g2/KgRwX41 d5PQ6VHkp4HA7L5Pw4ozlu8covsof1s1bPdoTqqJYdBQSYzjrGs1DMkK9N1Qor7M lgIpcOxEKlRTuxpHyIXK11Tjkqz7J+7RsN+3+456XfNE8DScD5+xrZ2vk67Jh6oT h76VhxY5IPSC7/OJsfAJW6kpa3Ur43WYEki27K4Nz/jUOKpjuy3j2nCbR4Fct7l/ 73JL7+VRDK1zUIjFj4GMI3riJUZwQWAF4kisMw3NVSvLkWUiXuTju4I0sisu475N xvD9bBFwefxydeBUeuF9EMa1B/4Vt4q4kfodX8XTV43KyUL5+qIEWCn+N5i4J5L4 xax7bs5wJnN2ezGdhqXkIsOHWglLAakvA4uUdelaJYL1wP47zGoIPLS2Dmv1PkKH 6DVEJfpRfzBCFqP1zsdRkmfn6A0Moa3kVLIZM7ETav9OPsLJ9u2NzjW9JqXv/z1t c7GIlwGcnhQcOKO7j4E4wueVIpFzpdzgE5GPTSp+08ILSMaGYiccy/L/o6c6mcg/ jfr77Iz5m+yLnpI1MTMqkFknfd59102C4oT6ddB2+q1UXQ1Q2ZI=
    =fL6V
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)