From owner-freebsd-x11@FreeBSD.ORG Sun Feb 22 21:49:58 2009 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 05AEE10656ED for ; Sun, 22 Feb 2009 21:49:57 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail1.es.net [IPv6:2001:400:201:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5D22C8FC18 for ; Sun, 22 Feb 2009 21:49:57 +0000 (UTC) (envelope-from oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id n1MLnuQi024051 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sun, 22 Feb 2009 13:49:56 -0800 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 54C281CC0B for ; Sun, 22 Feb 2009 13:49:26 -0800 (PST) To: x11@freebsd.org Date: Sun, 22 Feb 2009 13:49:26 -0800 From: "Kevin Oberman" Message-Id: <20090222214926.54C281CC0B@ptavv.es.net> Cc: Subject: New xorg and fvwm2 have mouse issues X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Feb 2009 21:49:59 -0000 This may be similar to other reported problems with mouse HAL, and Xorg inter-operation, but it seems different enough that I thought I'd report it in hopes that someone else has seen it. The problem occurs when doing a cut and paste. The selection works fine, but, when the mouse is moved to a new window to paste, the mouse locks up. If the process owning the cut window is killed, the mouse returns to normal operation. I have only seen this a co-worker's system. It is running DBUS, HAL, and has "AllowEmptyInput" "off". The only thing different from other systems is that it is not running metacity and Gnome. It is running fvwm2. It appears that something fvwm2 does with X in the cut and paste operation is hanging. Any ideas of what to look at and how to approach debugging it. It amy be that the problem is in fvwm2. I know that Tk required an update to work properly with the new Xorg. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751