From owner-freebsd-hackers Sun Oct 12 11:02:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA06270 for hackers-outgoing; Sun, 12 Oct 1997 11:02:30 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from euthyphro.uchicago.edu (euthyphro.uchicago.edu [128.135.21.31]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA06262; Sun, 12 Oct 1997 11:02:16 -0700 (PDT) (envelope-from sfarrell@phaedrus.uchicago.edu) Received: from phaedrus.uchicago.edu (phaedrus [128.135.21.10]) by euthyphro.uchicago.edu (8.8.6/8.8.4) with ESMTP id NAA01073; Sun, 12 Oct 1997 13:02:04 -0500 (CDT) Received: (from sfarrell@localhost) by phaedrus.uchicago.edu (8.8.7/8.8.5) id NAA12209; Sun, 12 Oct 1997 13:01:59 -0500 (CDT) To: freebsd hackers Cc: "Eric L. Hernes" Subject: gimp 0.99.13 From: stephen farrell Mime-Version: 1.0 (generated by tm-edit 7.89) Content-Type: text/plain; charset=US-ASCII Date: 12 Oct 1997 13:01:58 -0500 Message-ID: <87bu0uj1wp.fsf@phaedrus.uchicago.edu> Lines: 18 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I compiled gimp 0.99.13 (the latest development version) on my fbsd system (very recent FreeBSD 2.2-STABLE) and it dies before startup with: ** ERROR **: could not attach to gimp shared memory segment Now I have the appropriate shm stuff in my kernel and I was running 0.99.10 (the port) recently with no problems. Does anyone know why this happens? The obvious workaround (running gimp --no-shm and --no-xshm does work, btw). -- Steve Farrell