Carey Bunks wrote:
Dear GIMPsters,
Creating digital collage and photo-montage with the GIMP requires good
access to unfettered, raw photographic materials. Although there are
many online stock-photo companies offering images for a fee, to
promote and accelerate the use of the GIMP, it
Please can people put a quick explanation of why they're closing a bug
report into the close email. If it's fixed in CVS, a cut-n-paste of
the relevant ChangeLog entry that addresses the problem would be
cool. Otherwise, just a sentence or two would be enough.
Austin
Current gimp (1.1.21) seems to have problems with recovering from any
plugin that dies. Things start going wrong when it takes a SIGPIPE
while trying to write(read?) to the pipe to the plugin which is dead.
Rather than ignoring SIGPIPE, and collecting an EPIPE from the io
operation and using
On Mon, May 08, 2000 at 02:16:06PM +0100, Austin Donnelly wrote:
cleaned up on their unexpected termination at some earlier stage. The
whole point of plugins being separate processes is that a plugin
should be unable to cause the main gimp app to crash: if they can then
this is a fairly
Austin Donnelly wrote:
Current gimp (1.1.21) seems to have problems with recovering from any
plugin that dies. Things start going wrong when it takes a SIGPIPE
while trying to write(read?) to the pipe to the plugin which is dead.
Rather than ignoring SIGPIPE, and collecting an EPIPE from
On Sun, May 07, 2000 at 10:15:36PM -0700, Kevin Turner wrote:
Neat stuff.
Now to bug you for wish list stuff ;-
Is the photo credit for this image stored anywhere?
Hmmm, might be cool to have the ability to at least provide
all the info in a
I said:
The SIGPIPE problem is because on_signal is currently treating it as a
fatal signal (see the case on_signal in app/main.c). The on_signal routine
should probably be modified to not treat SIGPIPE as fatal. That should fix
the problem Austin is seeing (that others will no doubt see too).
Tim Mooney wrote:
In regard to: Re: EPIPE, Michael Natterer said (at 8:22pm on May 8, 2000):
Unfortunately this is not the reason why gimp dies on just any aborting
child. Although I 100% agree that SIGPIPE being fatal is the wrong thing
to do. I browsed CVS and Gimp is connecting SIGPIPE
Tim Mooney wrote:
I just looked at 1.1.19, and on_signal there was doing the same thing it
is now: SIGPIPE caused a call to gimp_terminate. Obviously the current code
is based on the older code.
So why is Austin observing the problem now? I'm not sure. It does seem
like it's behaving
