On 2017-02-15 14:31:43 +0100, Vincent Lefevre wrote: > When this happens, this is always with a special script. This may mean > that the bug occurs only under some particular conditions. One of them > that might matter is that the window title changes just before xterm > quits (new title: TITLEDISABLED).
I've noticed another difference: contrary to the other xterm processes, this one is no longer a descendent of the fvwm2 process. But the bug is reproducible even when I change my script to make xterm a descendent of fvwm2 (the script normally runs xterm in the background before quitting). 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. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
