Date: Sun, 7 Dec 2003 12:36:07 +0100 From: Viktor Vasilev <viktor@rbg.informatik.tu-darmstadt.de> To: freebsd-current@freebsd.org Subject: Re: gimp fails suddenly Message-ID: <20031207113607.GB301@rbg.informatik.tu-darmstadt.de> In-Reply-To: <200312070945.hB79jKds039814@www.kukulies.org> References: <200312070945.hB79jKds039814@www.kukulies.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[the first post didn't make it to current@] On Sun, Dec 07, 2003 at 10:45:20AM +0100, C. Kukulies wrote: > I cvsuped and built, installed world and kernel without a hitch > also did a port make index, portupgrade -aFrR. > > But when starting gimp this morning, I get: > > gimp > > LibGimp-ERROR **: could not attach to gimp shared memory segment > > aborting... > > LibGimp-WARNING **: gimp: wire_read: unexpected EOF > gimp: Plug-In crashed: "script-fu" > (/usr/X11R6/libexec/gimp/1.2/plug-ins/script-fu) > > The dying Plug-In may have messed up GIMP's internal state. > You may want to save your images and restart GIMP > to be on the safe side. > > ----- > > Could it be a mmap or vm problem? > I saw the same error yesterday on FreeBSD 4.9 Release and found a closed PR about it. The workaround was to start gimp with the --no-shm option. Have a nice day, Viktor -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031207113607.GB301>