Re: Clarification: Crashing X/Gnome with gimp

[Havoc Pennington <rhp zirx pair com>]

On Wed, 9 Jun 1999, Tod Liebeck wrote:
> 
> I think I need to explain myself a little more.  First off, I shouldn't
> have used the term "Crashing" with regard to X.  Rather, when the Gimp
> crashes, it simply hangs MOST of X.  My panel afterstep clock, cpu
> meter, etc, keep on ticking.  The mouse cursor continues to change shape
> as dictated by the window manager.... but that's about all X can do once
> this happens.  No mouse clicks or keyboard input is accepted by any
> application.  Windows don't focus when moused over, etc.  I then have to

Oh, this is caused by Gimp. When Gimp crashes it has the pointer
"grabbed," to keep you from interacting with other apps. Gimp isn't
exiting, because it's waiting for you to choose [S]tack trace, [P]roceed,
etc. If you simply kill the Gimp, then the problem should go away.

In general you should always be able to fix this problem by killing the
app that caused it. Often it will go away if you iconify the offending
window too, though you might have to use a key shortcut to do that.

It's possible that KDE starts gimp with /dev/null on stdin or something,
so that Gimp exits instead of waiting for input - this is just wild
speculation though. We might should do that for Gnome too.

Anyway, if killing Gimp doesn't fix it then I'm mystified. Let us know
what happens.

Havoc