From owner-freebsd-ports@FreeBSD.ORG Fri Nov 28 04:30:07 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBAAC16A4CE for ; Fri, 28 Nov 2003 04:30:07 -0800 (PST) Received: from lists.frmug.org (frmug-gw.frmug.org [193.56.58.252]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37EEF43FAF for ; Fri, 28 Nov 2003 04:30:05 -0800 (PST) (envelope-from olive@oban.frmug.org) Received: by lists.frmug.org (Postfix/TLS, from userid 66) id BCAFA20F39; Fri, 28 Nov 2003 13:30:04 +0100 (CET) Received: by weirdos.oban.frmug.org (Postfix, from userid 1002) id D2DA68C64; Fri, 28 Nov 2003 13:25:11 +0100 (CET) Date: Fri, 28 Nov 2003 13:25:11 +0100 From: Olivier Tharan To: ports@freebsd.org Message-ID: <20031128122511.GL46227@weirdos.oban.frmug.org> Mail-Followup-To: ports@freebsd.org References: <200311281025.hASAOx5r001739@peedub.jennejohn.org> <10580000.1070016805@rambutan.pingpong.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <10580000.1070016805@rambutan.pingpong.net> X-Attribution: Olive Subject: Re: firebird and xemacs locking up/crashing "in pairs"??? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Nov 2003 12:30:07 -0000 * Palle Girgensohn (20031128 11:53): > When switching workspaces using keyboard shortcut, if the mouse pointer is > placed so it is over two firebird windows, X cannot decide on which window > to focus, and switches focus between the two windows as fast as it can, > more than ten times / s, until I manually click a window title bar to force > focus. I've never seen this happen ever before, but I've not used gtk2 much > until now. See "image" for a clearer description :) mouse pointer is the I've seen it happen many times on older versions of WindowMaker. I don't know if that is still the case, nor in which conditions it happens (basically when something unexpected occurs with a window manager, the first suspect is the NumLock key :). -- olive