[Fvwm-crystal-users] The cleanup for FvwmMFL is maybe too eager

[Gianni C. <da...@th...>]

Hello!

I just updated to fvwm3, and noticed a small problem:

https://github.com/fvwm-crystal/fvwm-crystal/blob/main/fvwm/components/functions/LoadCommonStuffs#L20-L25

cleans up possibly-left-over sockets and pid-files before starting
``FvwmMFL``

This is fine when first starting on a new X session.

It is less fine when *restarting* fvwm3: the net effect is that the
socket is gone, but ``FvwmMFL`` is still running, and there's no way to
talk to it.

If I comment out those two ``PipeRead`` lines, everything works after
a restart.

-- 
	Dakkar - <Mobilis in mobile>
	GPG public key fingerprint = A071 E618 DD2C 5901 9574
	                             6FE2 40EA 9883 7519 3F88
	                    key id = 0x75193F88