168cf03a26db673503558e0518c1790911396fac is the first bad commit commit 168cf03a26db673503558e0518c1790911396fac Author: Michael Banack <bob5972@banack.net> Date: Wed Aug 5 07:11:17 2020 -0700 Fix errorTrap leak in free_win_data
I didn't set a custom vblank_mode but don't know how to verify this atm. And yes, reverting 168cf03a fixes it for me. BTW Debian's xfwm4-4.14.2 works fine. This was my starting point for the bisect run.
(xfwm4:2391): Gdk-ERROR **: 13:48:55.164: The program 'xfwm4' received an X Window System error.This probably reflects a bug in the program.The error was 'RenderBadPicture (invalid Picture parameter)'.(Details: serial 11553 error_code 143 request_code 139 (RENDER) minor_code 7)(Note to programmers: normally, X errors are reported asynchronously;that is, you will receive the error a while after causing it.To debug your program, run it with the GDK_SYNCHRONIZE environmentvariable to change this behavior. You can then get a meaningfulbacktrace from your debugger if you break on the gdk_x_error() function.)Sandbox: unsupported fd-relative fstatat(29, "", 0x7FFEBE0C7030, 4096)Sandbox: seccomp sandbox violation: pid 2809, tid 2809, syscall 262, args 29 139937633940222 140732086906928 4096 4096 1.xfwm4-Message: 13:48:56.559: Prefer XPresent with Mesa DRI Mobile Intel® GM45 Express Chipset (CTG)
None of the proposed xfconf-queries helped really.
Right, that explains it then. Basically, the bug 168cf03a fixes papers over that Xerror, which explains why reverting 168cf03a restores the functionality for you.
Ideally, you would:
To debug your program, run it with the GDK_SYNCHRONIZE environmentvariable to change this behavior. You can then get a meaningfulbacktrace from your debugger if you break on the gdk_x_error() function.
Meahwhile, can you please attach the output of xdpyinfo -queryExtensions on your system?