On 2024.09.05 09:22, Michael wrote:

Since I upgraded to KDE Frameworks 6 I have observed some rather
unwanted
window behaviours.

1. Window Interaction with Gkrellm

[snipped lots ....]

The latest release of gkrellm seems to have been over three years ago,
and unfortunately, I suspect there might not be another. The primary developer died three and a half years ago, and while there is still
some minor activity (or at least was last time I looked) nobody had
stepped up to fully take over. The current version still uses gtk+2,
and based on the discussions, the way the program works is rather
deeply embedded in the lower levels thereof, and the port to gtk+3 (or
even 4) will not be easy.

[I did not start a new thread, intending this just as a heads up in
case any of the discovered causes of the posted problems end up due to anything actually in gkrellm rather then in the new KDE workings.]

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

Thanks Jack,

On Thursday 5 September 2024 21:30:54 BST Jack wrote:

On 2024.09.05 09:22, Michael wrote:

Since I upgraded to KDE Frameworks 6 I have observed some rather
unwanted
window behaviours.

1. Window Interaction with Gkrellm

[snipped lots ....]

The latest release of gkrellm seems to have been over three years ago,
and unfortunately, I suspect there might not be another. The primary developer died three and a half years ago, and while there is still
some minor activity (or at least was last time I looked) nobody had
stepped up to fully take over. The current version still uses gtk+2,
and based on the discussions, the way the program works is rather
deeply embedded in the lower levels thereof, and the port to gtk+3 (or
even 4) will not be easy.

[I did not start a new thread, intending this just as a heads up in
case any of the discovered causes of the posted problems end up due to anything actually in gkrellm rather then in the new KDE workings.]

I was aware the developer passed and the future of Gkrellm is uncertain. I expect I will find using a PC without it *very* frustrating. The problems I was alerted to look into over the years because of some indication in Gkrellm are too many to mention. I hope someone comes forward and refactors the code in time.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmbaF3YACgkQseqq9sKV ZxmwBBAA1zof7qiIc/YBcuofDy2fs2XYp/LTF+3ZQp+KoWTf3Mc74Koc368VjqqD iSdrMD1R2LC8iie2y7fmgbySrv6BISooM5FrGO5iUzvK9/jtkCkZqejo4IELm5GJ gSxGrQMbsew6iSEaew/Mkqf6M5u+YyQhE7Tv5p40f4xjLG22R/VvfB9eIbQ1EVLq HNnkkBgGG9SkUSHJahiJBvn3PFDj1/BmmtJVbLg2kvLD/05jbPF7NZGhbozGehPi lR8bF25ufraYSmVTnCVSX+Ek3zcwcfsmj85X3MFyZECagWDppYNZoVqSf2mFoIJ4 fNXIAZIQ3uPHtvQsAPZNPRXhT+Cw2dNKKH7XpiigPn1EiiDBq5j9Naxsj4jVMS7a pAy0PZvZOFmLYClXfAXehPMaHKILv/XPe5ZO2Keyy68U9pCqWdpHYURIk5pqt45H EFaCAN9uoda8aeW4FDyAPE2s8oOOaAIVRAZc89VSuSDzhab6SV56dyMtwt/UDyg2 rOei+kmP4vVixefLngfFdGfFRB3sFW9F9EgPtTAs06FtmqMzw/FEmO7yHrZaVz2Z 9AIkSrrckAWKUFxwtqfefb+8/9c8lg7ZzrC5Qs+cmfhWJB5eDE098vJT3NlSM/jr fRLtoib3MbHbvnu9u3V3O3Z4LbYlyUiTA/WracrHIGOxJCi+FD4=
=T4X9
-----END PGP SIGNATURE-----

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