On Thu, Feb 16, 2017 at 9:24 AM, Vincent Lefevre <vinc...@vinc17.net> wrote: > On 2017-02-15 15:10:19 +0100, Vincent Lefevre wrote: >> It seems that the window remains on screen until some particular >> fvwm operation makes it disappear. In particular, I have: >> >> Mouse 0 1 A Windowops-or-Die >> >> where Windowops-or-Die opens a menu. I was getting this menu >> when I clicked on the title-bar button 1, but when I selected >> "Module FvwmIdent", the window disappeared. > > Running the xprop utility (without arguments) also makes the > window disappear. >
I recall some issue similar to this, but it only appeared with a patch I was testing that is not included. In my normal setup I have not experienced this issue and was not able to reproduce it without that patch I was testing. In order to try to provide upstream with the best info I can can you try two things. 1) First, what is your method of closing the xterm window? Does it use a mouse binding that includes a function that is waiting for a double click or hold event (+D or +H). This will cause a delay in fvwm closing the window as fvwm needs to wait to ensure determine what event gets triggered. Though your description seems to be something different, but I just wanted to rule this possibility out. 2) Can you produce this using the default-config or a minimal config and provide instructions so I can reproduce it? I tried running your xterm command and just get errors about the option "-" not being recognized. Thanks for the report, jaimos
