Bug#256863: This bug can probably be closed
Branden Robinson <[EMAIL PROTECTED]> writes: [...] > Well, I think what the code does is make buttons that were formerly > numbered 6 and 7 numbered 4 and 5 instead. Ah, that sounds right. >> > How recently did you notice this change in scroll wheel behavior? >> > What version of the xfree86 packages were you running previously? >> >> Very recently (in the last couple of weeks). So September 2003 >> doesn't seem possible. I've been running unstable for about a year, >> (updating most days) so I've presumably been running 4.2.1-12 and >> later for a long time. > > You didn't happen to have your X server up for a good 8--10 months, did > you? No, that can't be it. I was running X from an experimental source for a while, so I guess it's possible that I somehow missed it before. It doesn't feel likely, but these things happen. Anyway, everything's working now with the mouse. [...]
Bug#256863: This bug can probably be closed
On Fri, Jul 09, 2004 at 10:38:37AM +0100, Bruce Stephens wrote: > Branden Robinson <[EMAIL PROTECTED]> writes: > > [...] > > > I wonder if this would be explained by the following changelog entry: > > > > xfree86 (4.2.1-12) unstable; urgency=high > > [...] > > * patch #097: new; add Bartosz Zapalowski's patch for supporting wheel > > mice > > with large numbers of buttons; the ZAxisMapping option "pushes up" the > > other buttons so that the mouse behaves sanely. This addresses problems > > with how the X server parses wheel data from at least some devices that > > use the ExplorerPS/2 protocol. (Closes: #166550) > > [...] > > -- Branden Robinson <[EMAIL PROTECTED]> Tue, 30 Sep 2003 15:34:48 -0500 > > Could be that. The changelog doesn't describe the behaviour I saw, > but it certainly looks like the right area of code. Well, I think what the code does is make buttons that were formerly numbered 6 and 7 numbered 4 and 5 instead. > > How recently did you notice this change in scroll wheel behavior? > > What version of the xfree86 packages were you running previously? > > Very recently (in the last couple of weeks). So September 2003 > doesn't seem possible. I've been running unstable for about a year, > (updating most days) so I've presumably been running 4.2.1-12 and > later for a long time. You didn't happen to have your X server up for a good 8--10 months, did you? :) -- G. Branden Robinson| I'm not going to waste my precious Debian GNU/Linux | flash memory with Perl when I can [EMAIL PROTECTED] | do so much more with it. http://people.debian.org/~branden/ | -- Joey Hess signature.asc Description: Digital signature
Bug#256863: This bug can probably be closed
Branden Robinson <[EMAIL PROTECTED]> writes: [...] > I wonder if this would be explained by the following changelog entry: > > xfree86 (4.2.1-12) unstable; urgency=high > [...] > * patch #097: new; add Bartosz Zapalowski's patch for supporting wheel mice > with large numbers of buttons; the ZAxisMapping option "pushes up" the > other buttons so that the mouse behaves sanely. This addresses problems > with how the X server parses wheel data from at least some devices that > use the ExplorerPS/2 protocol. (Closes: #166550) > [...] > -- Branden Robinson <[EMAIL PROTECTED]> Tue, 30 Sep 2003 15:34:48 -0500 Could be that. The changelog doesn't describe the behaviour I saw, but it certainly looks like the right area of code. > How recently did you notice this change in scroll wheel behavior? > What version of the xfree86 packages were you running previously? Very recently (in the last couple of weeks). So September 2003 doesn't seem possible. I've been running unstable for about a year, (updating most days) so I've presumably been running 4.2.1-12 and later for a long time.
Bug#256863: This bug can probably be closed
tag 256863 + moreinfo thanks On Tue, Jun 29, 2004 at 04:42:19PM +0100, Bruce Stephens wrote: > If I change the ZAxisMapping line to > >Option "ZAxisMapping" "4 5" > > then scrolling works, and the other buttons become button-6 and 7. So > I think it's quite likely that previously the ZAxisMapping line (the > one mapping to "6 7") was being misread, and in fact the wheel was > always being mapped to "4 5". I wonder if this would be explained by the following changelog entry: xfree86 (4.2.1-12) unstable; urgency=high [...] * patch #097: new; add Bartosz Zapalowski's patch for supporting wheel mice with large numbers of buttons; the ZAxisMapping option "pushes up" the other buttons so that the mouse behaves sanely. This addresses problems with how the X server parses wheel data from at least some devices that use the ExplorerPS/2 protocol. (Closes: #166550) [...] -- Branden Robinson <[EMAIL PROTECTED]> Tue, 30 Sep 2003 15:34:48 -0500 How recently did you notice this change in scroll wheel behavior? What version of the xfree86 packages were you running previously? -- G. Branden Robinson| The last Christian died on the Debian GNU/Linux | cross. [EMAIL PROTECTED] | -- Friedrich Nietzsche http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Processed: Re: Bug#256863: This bug can probably be closed
Processing commands for [EMAIL PROTECTED]: > tag 256863 + moreinfo Bug#256863: xserver-xfree86: Mouse wheel no longer scrolls things, mouse has more buttons than is usual There were no tags set. Tags added: moreinfo > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#256863: This bug can probably be closed
If I change the ZAxisMapping line to Option "ZAxisMapping" "4 5" then scrolling works, and the other buttons become button-6 and 7. So I think it's quite likely that previously the ZAxisMapping line (the one mapping to "6 7") was being misread, and in fact the wheel was always being mapped to "4 5". That still leaves the vanishing sawfish bindings as a mystery, but they're dynamic, so it's not impossible to imagine them going, and it's of no particular consequence anyway.
