Created attachment 7863 debug log file xfwm 4.13.0 has no issues, 4.13.1 doesnt start: as it errors out on eventFilterAddWin(). DBG[event_filter.c:253] eventFilterAddWin(): error code: 2 Ignoring the error code allows it to start but then lots of things are broken at runtime, see attached debug log. This is on OpenBSD where there's no DRI3/Xpresent and other fancy things: Build Configuration for xfwm4 version 4.13.1 revision 942156e4: Startup notification support: yes XSync support: no Render support: yes Xrandr support: yes Xpresent support: no Embedded compositor: yes Epoxy support: yes KDE systray protocol proxy: no Happy to provide more debug info or try patches ofc.
xi2 is available and built by default, so maybe something related to xi2 handling added in 6013f1ee ?
XI2 support is definitely the issue, as 4.13.1 works perfectly fine if if disable XI2 at build time by setting ac_cv_lib_Xi_XISelectEvents=no in the build env.
Data point - the gtk3 build configuration is the following: GTK+ 3.22.30 =========== GDK backends: x11 X11 extensions: XKB Xinerama XI2.2 XRANDR XFIXES Composite DAMAGE So XI2 is enabled in gtk itself.
Might be fixed by https://bugzilla.xfce.org/attachment.cgi?id=7976
*** This bug has been marked as a duplicate of bug 14695 ***