Bug 19951

Summary: moused has problems with XFree86
Product: Base System Reporter: ritsch_p <ritsch_p>
Component: miscAssignee: jmz
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description ritsch_p freebsd_committer freebsd_triage 2000-07-15 20:00:01 UTC
since the installation of XFree86 4.0.1, it has a very annoying bug:
when launched, X has no problem with the mouse (a logitech ps/2 mouse)
but when exiting an xdm session, the mouse freezes and won't move anymor

How-To-Repeat: using Protocol AUTO and Device Sysmouse in /etc/XF86Config
with moused running inFreeBSD 4.1-RC
Comment 1 Jose M. Alcaide 2000-07-17 10:29:01 UTC
ritsch_p@FreeBSD.ORG wrote:
> 
> >Description:
> since the installation of XFree86 4.0.1, it has a very annoying bug:
> when launched, X has no problem with the mouse (a logitech ps/2 mouse)
> but when exiting an xdm session, the mouse freezes and won't move anymor
> >How-To-Repeat:
> using Protocol AUTO and Device Sysmouse in /etc/XF86Config
> with moused running inFreeBSD 4.1-RC
> >Fix:
> 

I bumped into this problem, too. However, I think it is not related to
moused, since when using protocol "Auto" and device "/dev/psm0" (i.e., no
moused running), the mouse gets frozen after CTRL-ALT-Fn switching.
It seems that protocol "Auto" does not work correctly, despite of
the mouse device.

Try to set protocol "MouseSystems" in your XF86Config. Surprisingly,
protocol "SysMouse" does no work for me with XFree86 4.0.1 and moused.

-- JMA
****** Jose M. Alcaide  //  jose@we.lc.ehu.es  //  jmas@FreeBSD.org ******
** "Beware of Programmers who carry screwdrivers" --  Leonard Brandwein **
Comment 2 Sheldon Hearn freebsd_committer freebsd_triage 2000-07-17 17:48:57 UTC
Responsible Changed
From-To: freebsd-bugs->jmz

Jean-Marc's port.
Comment 3 mikehan 2000-08-10 05:34:09 UTC
Hi, I've been having the same problem. I checked out the xc tree from
xfree86.org via cvs and looked at the commit logs for the XFree86
repository. It looks like this is supposed to be the fix:

http://www.xfree86.org/pipermail/cvs-commit/2000-August/000149.html

Since only xf86Option.c was modified, I generated a patch via:

xc/programs/Xserver/hw/xfree86/common> cvs diff -u -r 1.18 -r 1.19 xf86Option.c

and got this output:

<<EODIFF
Index: xf86Option.c
===================================================================
RCS file: /cvs/xc/programs/Xserver/hw/xfree86/common/xf86Option.c,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- xf86Option.c        2000/08/04 21:07:11     1.18
+++ xf86Option.c        2000/08/09 16:30:22     1.19
@@ -1,4 +1,4 @@
-/* $XFree86: xc/programs/Xserver/hw/xfree86/common/xf86Option.c,v 1.18 2000/08/04 21:07:11 tsi Exp $ */
+/* $XFree86: xc/programs/Xserver/hw/xfree86/common/xf86Option.c,v 1.19 2000/08/09 16:30:22 tsi Exp $ */
 
 /*
  * Copyright (c) 1998 by The XFree86 Project, Inc.
@@ -190,7 +190,7 @@
 pointer
 xf86ReplaceIntOption(pointer optlist, char *name, int val)
 {
-    char tmp[16];
+    char *tmp = xnfalloc(16);
     sprintf(tmp,"%i",val);
     return xf86AddNewOption(optlist,name,tmp);
 }
EODIFF

Maybe this patch should be applied to the XFree86-4 port until the
XFree86 people release the next version?
-- 
mikehan@best.com                               http://www.mikehan.com/
coffee achiever                              San Francisco, California
"I was thinking of the immortal words of Socrates, who said, "I drank what?"
Comment 4 jmz freebsd_committer freebsd_triage 2001-07-27 01:48:27 UTC
State Changed
From-To: open->closed

The problem is fixed in XFree86-4.1.0