On 31/05/2024 15:10, Vincent Lefevre wrote:
https://github.com/flatpak/xdg-desktop-portal/issues/999
I'm wondering whether there could be a same cause.
I can imagine that mutt may start a GUI handler for some attachment and
that application uses XDG desktop portal. However I would expect that
mutt just creates a file in /tmp, so it should not prevent mutt from
quit on SIGTERM. Desktop environment should ensure that the handler runs
independently of the mutt process (not as a child). Moreover that
application should be stopped earlier during shutdown.
Do you see an attempt to send SIGTERM to mutt before timeout and
SIGKILL? What other processes survived first step? Are there something
suspicious before SIGKILL stage?
