From owner-freebsd-bugs  Mon Nov 18 18:42:09 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id SAA07937
          for bugs-outgoing; Mon, 18 Nov 1996 18:42:09 -0800 (PST)
Received: from central.picker.com (central.picker.com [144.54.31.2])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA07926
          for <bugs@freebsd.org>; Mon, 18 Nov 1996 18:41:52 -0800 (PST)
Received: from ct.picker.com by central.picker.com with smtp
	(Smail3.1.28.1 #3) id m0vPg49-0004ruC; Mon, 18 Nov 96 21:37 EST
Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1)
	id AA25594; Mon, 18 Nov 96 21:35:06 EST
Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4)
	id VAA18897; Mon, 18 Nov 1996 21:34:35 -0500
Message-Id: <Mutt.19961118213434.rhh@ct.picker.com>
Date: Mon, 18 Nov 1996 21:34:34 -0500
From: rhh@ct.picker.com (Randall Hopper)
To: bugs@freebsd.org
Subject: [2.2-ALPHA] moused / X conflict
X-Mailer: Mutt 0.51
Mime-Version: 1.0
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

     (I just joined the list a few minutes ago, so I don't know if this
specific problem has been mentioned yet or not.)

     Just installed 2.2-ALPHA w/ XFree 3.2 this weekend.  After installing
fvwm2, every few minutes my window focus would stop tracking with my mouse
(I have pointer-focus configured).  It appeared to recognize buttons
pressed as those would highlight in the xterm over across the screen that
was stuck with focus.  Shifting back to a terminal screen and back
(Ctrl-Alt-F1/F4) didn't fix it.  The only two ways I found that did were
killing and restarting the X server, and hitting both mouse buttons at the
same time (I have Emulate3Buttons set).  

     Tried fvwm1 -- same problem.  At one point it quit listening to the
mouse altogether.  The X server was still alive (xperfmon kept updating),
tha machine was still alive (I could switch out to the virtual screens,
though I was getting when I typed were some strange control and high-bit
characters instead of what I was typing -- like some kind of shift state
was still active), but no mouse.  I then remembered having turned moused on
in sysconfig.

     I killed it and disabled it in sysconfig.  No problems since.  There's
no manpage on moused that I could find.

     Here's what I think is relevent config.  If I left something out that
would be useful to know, let me know:

     FreeBSD:  2.2-ALPHA
   sysconfig:  mousedtype=microsoft
     Mouse  :  Microsoft Serial Mouse 2.0A (2 button)
     Vidcard:  Stingray 64/Video 2Meg
     XFree  :  SVGA server, v3.2
  XF86Config:  Section "Pointer"
                   Protocol    "Microsoft"
                   Device      "/dev/cuaa0"
                   Emulate3Buttons
               EndSection

By the way, I never got to doing a "vidcontrol -m on".  This all happened
with moused in its default state.

Randall Hopper
rhh@ct.picker.com