From owner-freebsd-current@FreeBSD.ORG Fri Dec 12 06:36:17 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 823FD16A4CE for ; Fri, 12 Dec 2003 06:36:17 -0800 (PST) Received: from www.kukulies.org (www.kukulies.org [213.146.112.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id A954643D32 for ; Fri, 12 Dec 2003 06:36:15 -0800 (PST) (envelope-from kuku@www.kukulies.org) Received: from www.kukulies.org (localhost [127.0.0.1]) by www.kukulies.org (8.12.10/8.12.6) with ESMTP id hBCEaBin020359; Fri, 12 Dec 2003 15:36:11 +0100 (CET) (envelope-from kuku@www.kukulies.org) Received: (from kuku@localhost) by www.kukulies.org (8.12.10/8.12.6/Submit) id hBCEaA2F020358; Fri, 12 Dec 2003 15:36:10 +0100 (CET) Date: Fri, 12 Dec 2003 15:36:09 +0100 From: "Christoph P. Kukulies" To: "Artem 'Zazoobr' Ignatjev" Message-ID: <20031212143609.GA20325@gilberto.physik.rwth-aachen.de> References: <200312070945.hB79jKds039814@www.kukulies.org> <1071238350.735.3.camel@timon.nist> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1071238350.735.3.camel@timon.nist> User-Agent: Mutt/1.4.1i cc: "C. Kukulies" cc: freebsd-current@freebsd.org Subject: Re: gimp fails suddenly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 14:36:17 -0000 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 -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de