Date: Fri, 12 Dec 2003 17:12:31 +0300 From: "Artem 'Zazoobr' Ignatjev" <timon@memphis.mephi.ru> To: "C. Kukulies" <kuku@www.kukulies.org> Cc: freebsd-current@freebsd.org Subject: Re: gimp fails suddenly Message-ID: <1071238350.735.3.camel@timon.nist> 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
On su, 07.12.2003, at 12:45, 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've found following advise after installing vmware3 port... That revived gimp back for me: sysctl -w kern.ipc.shm_allow_removed=1 I've put it into sysctl.conf, and run with it. -- Artem 'Zazoobr' Ignatjev <timon@memphis.mephi.ru>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1071238350.735.3.camel>