Created attachment 2208 [details] Scripts containing the three runs and some system configuration detail. The two scripts in the attachment demonstrate: webclient$claws-mail working without crashing. monitor$ssh -Y webclient claws-mail working without crashing. monitor$ssh -X webclient claws-mail crashing. In all three runs I opened a Compose window and pressed the 'down' navigation key. Some time ago, possibly at least two years, 'ssh -X ...' would not start claws-mail and I used 'ssh -Y ...'. As soon as I noticed 'ssh -X ...' would start claws-mail I changed monitor's .fvwmrc configuration file to use 'ssh -X ...' but did not see the problem until I had forgotten the change. Since then I just tried to avoid the problem keypresses at the wrong time until I tried 'ssh -Y ...' earlier today. (Note that webclient is a testing box which had claws-mail added earlier today specifically to do these demonstration runs.) Replacing webclient by a FreeBSD 13.0 box leads to the same problem. Apologies if I have chosen the wrong product (Claws Mail GTK-3 looked plausible too). I am not convinced about the component choice either, but that is where I encounter the problem most.
Created attachment 2209 [details] Script using Raspberrypi400 as Xserver for claws-mail on OpenBSD 6.9 'ssh -X webclient claws-mail' on Raspberrypi400 does not crash as described in previous post. Maybe the change in OpenSSH version is the thing that matters.
works fine here. Whatever the problem is, I don't think the problem resides in claws-mail.
Thanks for looking.
At https://www.scm.com/doc/Installation/Remote_GUI.html the "sidenote on ssh -X and -Y:" seems relevant. The behaviour I see is consistent with the statement "... some distros (...) disable them by default ..." being true.
I don't see what's relevant. If they are disabled by default they can still be re-enabled. When disabled they just don't work.