On 30-Jun-2002 xOr wrote: > On Sun, Jun 30, 2002 at 12:52:13PM +0300, Ciprian Popovici wrote: >> I did the following: >> * launch a terminal window >> * from it, launch another (ie. $ aterm) >> * the new terminal windows works ok, the old one is waiting for the >> other to finish in order to resume >> * in the first window I press ctrl-z and send the second to background >> * the second window "freezes" and cannot be killed or used >> * when I return to foreground in the first window ($ fg) the second >> one return to normal and resumes whatever was attempted (if kill was >> attempted, it finally dissapears). >> >> Is this normal? > > Yes. When you hit that close button, it tells the app to close. When its > stopped, it can't close until you resume it. >
To expound on this further. When you stop the app, it can no longer process events. The close button works by sending a "I want you to close" message to the client from the wm. The wm has the choice to ignore or delay the closing. For instance it may open a "save open files" dialog. When it woke up, the event was waiting in the queue.
