Bug#454546: Cause of problem, possible patch

2011-01-19 Thread Cyril Brulebois
tag 454546 upstream
thanks

Pigeon pig...@pigeonsnest.co.uk (14/12/2007):
 ...update since my last message: I have since had several
 unrecognised packet events recorded in the log, but both wheels have
 continued to work fine throughout.

Hi,

any update on this bug? It looks like the upstream bugreport is
waiting for some input from you? Anyway, you probably should be using
evdev nowadays:
  http://pkg-xorg.alioth.debian.org/howtos/configure-input.html

KiBi.


signature.asc
Description: Digital signature


Bug#454546: Cause of problem, possible patch

2007-12-14 Thread Pigeon
On Sat, Dec 08, 2007 at 01:11:10PM +0100, Brice Goglin wrote:
 Does both wheels work very fine with your patch?
 (apart from some unrecognized packet warnings in the Xorg log)

...update since my last message: I have since had several
unrecognised packet events recorded in the log, but both wheels
have continued to work fine throughout.

-- 
Pigeon

Be kind to pigeons- -Pigeon's Nest: http://pigeonsnest.co.uk/
GPG key: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x21C61F7F


signature.asc
Description: Digital signature


Bug#454546: Cause of problem, possible patch

2007-12-14 Thread Brice Goglin
forwarded 454546 https://bugs.freedesktop.org/show_bug.cgi?id=13662
thank you



Pigeon wrote:
 I will report your problem upstream. Does both wheels work very fine
 with your patch?
 (apart from some unrecognized packet warnings in the Xorg log)
 

 Because of the intermittent nature of the problem the warning has only
 appeared once since I installed the patch, but it has indeed occurred,
 and both wheels are still working fine. As far as I can tell there is
 no problem.
   


I have forwarded your problem at the URL above. Feel free to add any comment
if you think it could help.

Brice




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#454546: Cause of problem, possible patch

2007-12-14 Thread Pigeon
On Fri, Dec 14, 2007 at 11:36:45PM +0100, Brice Goglin wrote:
 I have forwarded your problem at the URL above. Feel free to add any comment
 if you think it could help.

These which I have just googled are probably relevant:

Probably related problem: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=392864

Reasoning behind the introduction of the problem code: 
https://bugzilla.novell.com/show_bug.cgi?id=144682

Copied to above bugzilla along with link to this bug.

-- 
Pigeon

Be kind to pigeons- -Pigeon's Nest: http://pigeonsnest.co.uk/
GPG key: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x21C61F7F


signature.asc
Description: Digital signature


Bug#454546: Cause of problem, possible patch

2007-12-12 Thread Pigeon
On Sat, Dec 08, 2007 at 01:11:10PM +0100, Brice Goglin wrote:
 Pigeon wrote:
  Looking at the source code for xserver-xorg-input-mouse it seems that this
  behaviour is a gross overreaction to the reception of a spurious z-axis
  packet from the mouse.
 
  if (pMse-negativeW != MSE_NOAXISMAP) {
  switch (pBuf[3]  0x0f) {
  case 0x00:  break;
  case 0x01: dz =  1; break;
  case 0x02: dw =  1; break;
  case 0x0e: dw = -1; break;
  case 0x0f: dz = -1; break;
  default:
  xf86Msg(X_INFO,
  Mouse autoprobe: Disabling secondary 
  wheel\n);
  pMse-negativeW = pMse-positiveW = 
  MSE_NOAXISMAP;
  }
  }
 
  So, if it receives any z-axis data that it does not understand, it does not
  simply ignore it, it immediately and for no reason nukes the secondary 
  wheel,
  and moreover does this in such a way that it also destroys any wheel 
  remapping,
  with the result that it also destroys my vertical wheel. This is very rude.
 
  So I am currently testing the following patch, which simply reports and then
  ignores the spurious packet, instead of making my mouse unusable.
 

 
 I will report your problem upstream. Does both wheels work very fine
 with your patch?
 (apart from some unrecognized packet warnings in the Xorg log)

Because of the intermittent nature of the problem the warning has only
appeared once since I installed the patch, but it has indeed occurred,
and both wheels are still working fine. As far as I can tell there is
no problem.

-- 
Pigeon

Be kind to pigeons- -Pigeon's Nest: http://pigeonsnest.co.uk/
GPG key: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x21C61F7F


signature.asc
Description: Digital signature


Bug#454546: Cause of problem, possible patch

2007-12-08 Thread Brice Goglin
Pigeon wrote:
 Looking at the source code for xserver-xorg-input-mouse it seems that this
 behaviour is a gross overreaction to the reception of a spurious z-axis
 packet from the mouse.

 if (pMse-negativeW != MSE_NOAXISMAP) {
   switch (pBuf[3]  0x0f) {
   case 0x00:  break;
   case 0x01: dz =  1; break;
   case 0x02: dw =  1; break;
   case 0x0e: dw = -1; break;
   case 0x0f: dz = -1; break;
   default:
   xf86Msg(X_INFO,
   Mouse autoprobe: Disabling secondary 
 wheel\n);
   pMse-negativeW = pMse-positiveW = 
 MSE_NOAXISMAP;
   }
 }

 So, if it receives any z-axis data that it does not understand, it does not
 simply ignore it, it immediately and for no reason nukes the secondary wheel,
 and moreover does this in such a way that it also destroys any wheel 
 remapping,
 with the result that it also destroys my vertical wheel. This is very rude.

 So I am currently testing the following patch, which simply reports and then
 ignores the spurious packet, instead of making my mouse unusable.

   

I will report your problem upstream. Does both wheels work very fine
with your patch?
(apart from some unrecognized packet warnings in the Xorg log)

Brice




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#454546: Cause of problem, possible patch

2007-12-06 Thread Pigeon
Looking at the source code for xserver-xorg-input-mouse it seems that this
behaviour is a gross overreaction to the reception of a spurious z-axis
packet from the mouse.

if (pMse-negativeW != MSE_NOAXISMAP) {
switch (pBuf[3]  0x0f) {
case 0x00:  break;
case 0x01: dz =  1; break;
case 0x02: dw =  1; break;
case 0x0e: dw = -1; break;
case 0x0f: dz = -1; break;
default:
xf86Msg(X_INFO,
Mouse autoprobe: Disabling secondary 
wheel\n);
pMse-negativeW = pMse-positiveW = 
MSE_NOAXISMAP;
}
}

So, if it receives any z-axis data that it does not understand, it does not
simply ignore it, it immediately and for no reason nukes the secondary wheel,
and moreover does this in such a way that it also destroys any wheel remapping,
with the result that it also destroys my vertical wheel. This is very rude.

So I am currently testing the following patch, which simply reports and then
ignores the spurious packet, instead of making my mouse unusable.


diff -u src/mouse.c.orig src/mouse.c 
--- src/mouse.c.orig2007-12-06 14:57:38.0 +
+++ src/mouse.c 2007-12-06 14:27:08.0 +
@@ -1511,9 +1511,14 @@
case 0x0e: dw = -1; break;
case 0x0f: dz = -1; break;
default:
+#ifdef notdef
xf86Msg(X_INFO,
Mouse autoprobe: Disabling secondary wheel\n);
pMse-negativeW = pMse-positiveW = MSE_NOAXISMAP;
+#else
+   xf86Msg(X_INFO,
+   ExplorerPS/2 decode: unrecognised z-axis packet 
received\n);
+#endif
   }
}
if (pMse-negativeW == MSE_NOAXISMAP)





-- 
Pigeon

Be kind to pigeons- -Pigeon's Nest: http://pigeonsnest.co.uk/
GPG key: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x21C61F7F


signature.asc
Description: Digital signature