RFR: 8338751: ConfigureNotify behavior has changed in KWin 6.2

Vlad Zahorodnii duke at openjdk.org
Wed Oct 16 23:45:20 UTC 2024


On Thu, 10 Oct 2024 11:50:52 GMT, Vlad Zahorodnii <duke at openjdk.org> wrote:

> Prior to 6.2, kwin used to always send synthetic ConfigureNotify events regardless whether a real ConfigureNotify event is going to be sent. It used to do it because of some bugs in GTK2.
> 
> In 6.2, that workaround was dropped (it was needed to fix other issues during interactive resize) so kwin adheres to ICCCM 4.1.5 now.
> 
> Unfortunately, it seems like JDK relies on kwin always sending synthetic configure notify events, which is no longer the case.
> 
> This change makes AWT use the TranslateCoordinates request when a real ConfigureNotify event is received and running kwin as the window manager. It should work as expected even with kwin < 6.2.

Thank you a lot for merging the patch. Also, if you have something kwin related that bothers you, please ping me (I'm a kwin maintainer). :)

---

Regarding this change though, can it be backported to the LTS branches (17 and 21) later? I made a workaround in kwin 6.2.1 but it's not bullet-proof and just covers some cases that are known to be broken.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/21449#issuecomment-2418147942


More information about the client-libs-dev mailing list