Maximized Xwayland apps all freeze after a while

[Botspot]

After having the latest PiOS Bookworm 64-bit running for a while on my Pi5, something happens and all maximized Xwayland apps begin to freeze.

Symptoms:

• I can still interact with the programs, copy text, use keyboard shortcuts, but this can be tricky because it must be done from memory. Affected programs do not display any visual updates - they appear frozen but the changing mouse cursor states prove otherwise.
• Affected programs ignore resize requests. If it starts maximized and I click the button to unmaximize, it can only relocate on the screen, and refuses to actually change its size.
• Xwayland apps that are not maximized are unaffected until you try to maximize them.

Causes:

• It is unknown what causes "the trigger event", but it seems global to the system. Once it occurs, the only known full solution is to reboot.
• Once "the trigger event" has happened, any maximized Xwayland program that has been minimized and then raised again will be frozen.
• Once "the trigger event" has happened, any non-maximized Xwayland program will freeze upon attempting to maximize it.
• Sometimes after enough tries, some Xwayland apps will seemingly refuse to launch at all, though their processes are running. Based on wmctrl output, it seems that the program windows are normal size and placement, but the windows are invisible and not even shown on the taskbar.

Timeline:

• For a while I had no idea what was going on, but one day I realized that the only affected apps were running under Xwayland.
• This has not always been an issue on PiOS Bookworm. I think it was a regression caused by one of your more recent Wayfire builds.

Affected apps:

• Arduino (known to be Xwayland)
• WPS Office (known to be Xwayland)
• ArmCord (known to be Xwayland)
• Puffin Browser (known to be Xwayland)
• Pi-Apps (less of an issue because it is not usually a maximized program)

I understand that this is likely hard to reproduce. It does not occur immediately after boot, and I doubt that leaving a system running idly for long enough would cause "the trigger event" to happen by itself. Wayfire is likely the issue here. I am not familiar with where Wayfire logs errors. Please respond with advice for where to view Wayfire logs on a running system. In the meantime, I will try to avoid rebooting my system so we can get to the bottom of this.

[Botspot]

Here's what it looks like when trying to maximize an Xwayland program after "the trigger event" has occured.

• Pi-Apps:
• Arduino:

[spl237]

Please respond with advice for where to view Wayfire logs on a running system.

I'm not aware of a way to do that. The way I get logs from wayfire is to boot to console, then start wayfire and pipe its output to a file - wayfire-pi > logfile.txt

Problems which are confined to Xwayland may be in the decoration plugin - you could try editing /etc/wayfire/defaults.ini and remove the item "pixdecor" from the 'plugins' line. You will then get no headerbar on Xwayland applications, but it would be useful to know if this fixes the problem.