Peter Daum wrote:
> is there any known issue with fvwm and multiple X servers?
[...]
In case anybody runs into a similar problem here's what I found out:
Multiple X servers per se don't seem to cause any trouble.
In my case the problem was a "Wait"-command in the InitFunction.
Fvwm got stuck waiting for an event that would not happen, and it
seems like no matter how this is aborted, (via the X server or for
example by invoking a window list via keyboard - the Escape-Function
didn't seem to do anything) fvwm is somewhat confused afterwards.
The simplest way to get things going again is restarting fvwm
(provided there is no "Wait" in the RestartFunction that causes
problems)
Regards,
Peter Daum
