On Fri, Dec 12, 2003 at 05:12:31PM +0300, Artem 'Zazoobr' Ignatjev wrote: > 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. That's fine. Just tell me, what does this actually mean? Is it practically the same as running gimp --no-shm ? Or is shm activated (like a module being not present and the getting loaded?). > Artem 'Zazoobr' Ignatjev <timon_at_memphis.mephi.ru> -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.deReceived on Fri Dec 12 2003 - 05:36:17 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:33 UTC