5 seconds seems long in the face of a user. But if the application does actually handle the termination signal, and needs more than 5 seconds for cleanup, does it mean the cleanup procedure will be interrupted/aborted, or is only the GUI connection disconnected?

In D3370#62908, @cfeck wrote:

5 seconds seems long in the face of a user. But if the application does actually handle the termination signal, and needs more than 5 seconds for cleanup, does it mean the cleanup procedure will be interrupted/aborted, or is only the GUI connection disconnected?

The GUI connection gets disconnected which will raise a Wayland error on client side. How the application handles this is toolkit specific. In case of QtWayland it will result in an ::exit(1)

And it's also no guarantee that the window will be gone. In case of Qt it works as the Wayland connection is hold in another thread, so if the main thread is frozen and cannot react to the sigterm, the destroy of the Wayland connection will still work.

So overall the 5 sec are a main-thread freeze protection and could be changed in whatever way we want.