From owner-freebsd-bugs Fri Feb 7 14:11:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA23110 for bugs-outgoing; Fri, 7 Feb 1997 14:11:12 -0800 (PST) Received: from vdp01.vailsystems.com (root@vdp01.vailsystems.com [207.152.98.18]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA23105; Fri, 7 Feb 1997 14:11:08 -0800 (PST) Received: from crocodile.vale.com (crocodile [204.117.217.147]) by vdp01.vailsystems.com (8.8.3/8.7.3) with ESMTP id QAA20190; Fri, 7 Feb 1997 16:10:59 -0600 (CST) Received: from slave1 (slave1.vale.com [204.117.217.100]) by crocodile.vale.com (8.8.3/8.7.3) with ESMTP id QAA03372; Fri, 7 Feb 1997 16:10:58 -0600 (CST) Message-ID: <32FBA862.5C74@vailsys.com> Date: Fri, 07 Feb 1997 16:10:42 -0600 From: Dan Riley Reply-To: driley@vailsys.com X-Sender: Dan Riley (Unverified) X-Mailer: Mozilla 4.0b1 (WinNT; I) MIME-Version: 1.0 To: Leonard Chua CC: freebsd-bugs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: moused and X11R6 X-Priority: Normal References: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Leonard Chua wrote: > > Anybody tried running moused on 2.2-BETA? > Works beautifully in console mode, > But when I run X, there seems to be a conflict with X's mouse events. > One reason may be that I have moused doing 2 button microsoft mode > and X doing 3 button mode. The mouse cursor at X works fine until I press > button 3. Then the mouse no longer responds. The rest of X still works. > A possible fix would be to hack moused to notice an X session and stop > capturing mouse events then. > > Cheers. > Len. The Xserver on my 2.2-Gamma system will not even start up with moused running, although I have no complaints about moused in console mode, it is a very nice feature from the linux-world. :)