Hi Tim!
On Di, 01 Aug 2017, Tim Bagot wrote:
> When I quit xfig by selecting "Exit" from the "File" menu, very often
> xfig's window is left behind (unresponsive) after the process has
> terminated. (I can fortunately kill the window with xkill.) This does
> not happen 100% reliably, and I cannot quite determine the precise
> circumstances that make it happen or not; but so far it does _not_
> appear to happen when a figure has been modified. (In other words, the
> save-before-quitting dialog box seems to prevent the problem.)
>
> Interestingly, if I move the dead window around, the File menu (which
> is still displayed) does not move with it, but stays fixed in the same
> position on the screen.
>
> This only affects quitting via the menu, not quitting using the Meta-Q
> keyboard shortcut or by closing the window.
Thanks for your bug report. I'm not fully sure, whether I fully
understand what you descripbe, since I never notice such a problem
with xfig before.
If I get you right, you start xfig (and optionally edit and save) and
then exit it via File->Exit. Instead of terminating, the xfig root
window stays open as some kind of zombie. Did I get this right?
Maybe this depends on the desktop environment? I myself still use
fvwm2 (maybe as old as xfig ;-).
Can you see via
ps -C xfig -lf
which state (second column) your xfig process(es) have when it behaves
like a zombie. While running you should see something like
F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD
0 S roland 15557 10495 0 80 0 - 1073 - 08:21 pts/20 00:00:00
/bin/sh /usr/bin/xfig
0 S roland 15564 15557 0 80 0 - 16575 SyS_po 08:21 pts/20 00:00:00
/usr/lib/xfig/xfig
What does it show in the zombie state?
Maybe we can find out what's going on here...
Greetings
Roland
