From owner-freebsd-questions@FreeBSD.ORG Sat Jun 30 00:57:06 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C5A4616A400 for ; Sat, 30 Jun 2007 00:57:06 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42]) by mx1.freebsd.org (Postfix) with ESMTP id 5D38F13C45B for ; Sat, 30 Jun 2007 00:57:06 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from epia-2.farid-hajji.net (epia-2 [192.168.254.11]) by fw.farid-hajji.net (Postfix) with ESMTP id BDE0BDF7D5; Sat, 30 Jun 2007 02:53:42 +0200 (CEST) Message-ID: <4685AAD3.8070506@cordula.ws> Date: Sat, 30 Jun 2007 02:58:59 +0200 From: cpghost User-Agent: Thunderbird 2.0.0.4 (X11/20070616) MIME-Version: 1.0 To: Momchil Ivanov References: <200706292249.48484.slogster@gmail.com> In-Reply-To: <200706292249.48484.slogster@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: gimp grashing: "The error was 'BadWindow (invalid Window parameter)'." X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jun 2007 00:57:06 -0000 Momchil Ivanov wrote: > Hi, > > I am running FreeBSD 6-STABLE as of Thu Jun 14 13:01:26 CEST 2007, Xorg 7.2 > and the gimp-2.2.15,2 port. I am experiencing the following problem: When I > create/open a document then select the brush and click in the document window > gimp crashed with the following error > > >> space@a144026 gimp$ gimp >> The program 'gimp' received an X Window System error. >> This probably reflects a bug in the program. >> The error was 'BadWindow (invalid Window parameter)'. >> (Details: serial 29816 error_code 3 request_code 39 minor_code 0) >> (Note to programmers: normally, X errors are reported asynchronously; >> that is, you will receive the error a while after causing it. >> To debug your program, run it with the --sync command line >> option to change this behavior. You can then get a meaningful >> backtrace from your debugger if you break on the gdk_x_error() >> function.) space@a144026 gimp$ >> (script-fu:32342): LibGimpBase-WARNING **: script-fu: wire_read(): error >> >> There was a bug in x11/libX11, which was fixed with /usr/ports/x11/libX11/files/patch-src::GetMoEv.c (IIRC around June 22) Just update your ports tree and recompile and reinstall x11/libX11 (e.g. with 'make && make deinstall && make reinstall). Then this specific bug should go away. > Does somebody else get the same error? Any ideas how can I fix this? > s. above. :-) Regards, -cpghost. -- Cordula's Web. http://www.cordula.ws/