097_mouse_zaxis_mapping_pushes_up_buttons should be dropped as of 6.9/7.0 RC3

Bug #27941 reported by Debian Bug Importer
6
Affects Status Importance Assigned to Milestone
xorg (Debian)
Fix Released
Unknown
xorg (Ubuntu)
Invalid
High
Daniel Stone

Bug Description

Automatically imported from Debian bug report #343728 http://bugs.debian.org/343728

Revision history for this message
In , Pekka Jääskeläinen (pekka-jaaskelainen) wrote : can you please tell how to get over this?

I think I bumped into this problem after the latest xserver update.

Previously my MS Intellimouse Optical worked perfectly: all its
buttons, including
the thumb buttons (for back and forward), and the wheel worked
perfectly in Mozilla.

After the upgrade, wheel and thumb buttons stopped working, and I got the wheel
working by commenting out following lines in xorg.conf, thus resorting
to their new
default values:

# Option "Buttons" "7"
# Option "ZAxisMapping" "6 7"

Can you please give instructions for getting also the thumb buttons to
work again? I don't understand how that ZAxisMapping thing is supposed
to work with my mouse.

Thanks,
--
--PJ

Revision history for this message
In , Alexandre Ahmim-Richard (passe) wrote : Re: Bug#343728: can you please tell how to get over this?

Pekka Jääskeläinen wrote:
> I think I bumped into this problem after the latest xserver update.
>

Me too.

> Previously my MS Intellimouse Optical worked perfectly:
>

I've got the same mouse, same thing here.

> After the upgrade, wheel and thumb buttons stopped working, and I got the wheel
> working by commenting out following lines in xorg.conf, thus resorting
> to their new
> default values:
>
> # Option "Buttons" "7"
> # Option "ZAxisMapping" "6 7"
>
> Can you please give instructions for getting also the thumb buttons to
> work again? I don't understand how that ZAxisMapping thing is supposed
> to work with my mouse.
>

I've described the problem here :
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=345704

You can have your 5 first buttons working (so it includes the wheel).

Let: Option "Buttons" "7"
Set: Option "ZAxisMapping" "4 5"

And you are done.

You can also deactivate your xmodmap which should be pointer = 1 2 3 6 7 4 5
As described in my bugreport, X see 11 buttons on this mouse (that's the
main problem), xmodmap expects 11 buttons to be mapped, not 7.

If you also want to use your 2 specials left and right buttons, for all
I know, it's not actually possible.

--
Alexandre Ahmim-Richard
passe at clope dot net
http://www.u-admin.org

Revision history for this message
In , Christopher Martin (chrsmrtn-debian) wrote :

severity 343728 grave
stop

Since this patch is still included in the X.Org packaging in unstable,
imwheel is now broken. Please drop the patch (made obsolete by upstream
changes, as explained below) in the next upload.

This link (and the links it contains) explains further:
https://bugs.freedesktop.org/show_bug.cgi?id=1900

Thanks,
Christopher Martin

On Saturday 17 December 2005 12:14, Christopher Martin wrote:
> Package: xserver-xorg
> Version: 6.8.99.903.dfsg.1-1
> Severity: normal
> Tags: experimental
>
> Debian's X.Org packaging includes the patch
> 097_mouse_zaxis_mapping_pushes_up_buttons.diff, which serves to adjust
> mouse button mappings so that users didn't have to use xmodmap to make
> all available physical buttons available for use.
>
> In X.Org 6.9/7.0 RC3, upstream made changes to the mouse button handling.
> The default ZAxisMapping is "4 5 6 7", accommodating scroll wheels with
> two axes. Also by default the mouse physical : logical button mapping is
> now "1 2 3 8 9 ...", so that all physical buttons can be used (thumb
> buttons are 8 and 9) without conflict with the scroll wheel.
>
> These changes make Debian's 097 patch obsolete, since now all buttons are
> properly exposed by default. Indeed, continuing to include the 097 patch
> causes problems, since the buttons are shifted around twice, and it all
> becomes very messy. (When wondering why imwheel stopped working with the
> latest experimental X, I read up on upstream's changes, and had to
> rebuild X without 097 to get the expected new behaviour).
>
> FYI, since you'll probably get questions/bug reports, this change in
> behaviour has other implications. Mozilla uses buttons 6 and 7 for
> "forward" and "back", but this doesn't work anymore, since those buttons
> are now assumed to represent the horizontal axis of the scroll wheel,
> whether your mouse has one or not. Users can of course use xmodmap or the
> new ButtonMapping xorg.conf option to work around this. As far as I can
> tell, Qt applications seem to use 6 and 7 for horizontal scrolling
> already, so they shouldn't generate too many reports of brokenness.
>
> Cheers,
> Christopher Martin
>
> I'd also like to append this obligatory nag to have bug #237877 looked at
> :)

Revision history for this message
In , Christopher Martin (chrsmrtn-debian) wrote :

tags 343728 - experimental
stop

Now in unstable.

On Tuesday 03 January 2006 17:42, Christopher Martin wrote:
> severity 343728 grave
> stop
>
> Since this patch is still included in the X.Org packaging in unstable,
> imwheel is now broken. Please drop the patch (made obsolete by upstream
> changes, as explained below) in the next upload.
>
> This link (and the links it contains) explains further:
> https://bugs.freedesktop.org/show_bug.cgi?id=1900
>
> Thanks,
> Christopher Martin

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Automatically imported from Debian bug report #343728 http://bugs.debian.org/343728

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Sat, 17 Dec 2005 12:14:01 -0500
From: Christopher Martin <email address hidden>
To: <email address hidden>
Subject: 097_mouse_zaxis_mapping_pushes_up_buttons should be dropped as of 6.9/7.0 RC3

Package: xserver-xorg
Version: 6.8.99.903.dfsg.1-1
Severity: normal
Tags: experimental

Debian's X.Org packaging includes the patch
097_mouse_zaxis_mapping_pushes_up_buttons.diff, which serves to adjust
mouse button mappings so that users didn't have to use xmodmap to make all
available physical buttons available for use.

In X.Org 6.9/7.0 RC3, upstream made changes to the mouse button handling.
The default ZAxisMapping is "4 5 6 7", accommodating scroll wheels with two
axes. Also by default the mouse physical : logical button mapping is now "1
2 3 8 9 ...", so that all physical buttons can be used (thumb buttons are 8
and 9) without conflict with the scroll wheel.

These changes make Debian's 097 patch obsolete, since now all buttons are
properly exposed by default. Indeed, continuing to include the 097 patch
causes problems, since the buttons are shifted around twice, and it all
becomes very messy. (When wondering why imwheel stopped working with the
latest experimental X, I read up on upstream's changes, and had to rebuild
X without 097 to get the expected new behaviour).

FYI, since you'll probably get questions/bug reports, this change in
behaviour has other implications. Mozilla uses buttons 6 and 7 for
"forward" and "back", but this doesn't work anymore, since those buttons
are now assumed to represent the horizontal axis of the scroll wheel,
whether your mouse has one or not. Users can of course use xmodmap or the
new ButtonMapping xorg.conf option to work around this. As far as I can
tell, Qt applications seem to use 6 and 7 for horizontal scrolling already,
so they shouldn't generate too many reports of brokenness.

Cheers,
Christopher Martin

I'd also like to append this obligatory nag to have bug #237877 looked at :)

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Wed, 4 Jan 2006 00:02:18 +0200
From: =?ISO-8859-1?Q?Pekka_J=E4=E4skel=E4inen?= <email address hidden>
To: <email address hidden>
Subject: can you please tell how to get over this?

I think I bumped into this problem after the latest xserver update.

Previously my MS Intellimouse Optical worked perfectly: all its
buttons, including
the thumb buttons (for back and forward), and the wheel worked
perfectly in Mozilla.

After the upgrade, wheel and thumb buttons stopped working, and I got the w=
heel
working by commenting out following lines in xorg.conf, thus resorting
to their new
default values:

# Option "Buttons" "7"
# Option "ZAxisMapping" "6 7"

Can you please give instructions for getting also the thumb buttons to
work again? I don't understand how that ZAxisMapping thing is supposed
to work with my mouse.

Thanks,
--
--PJ

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Tue, 03 Jan 2006 23:20:31 +0100
From: Alexandre Ahmim-Richard <email address hidden>
To: <email address hidden>, <email address hidden>
Subject: Re: Bug#343728: can you please tell how to get over this?

Pekka J=E4=E4skel=E4inen wrote:
> I think I bumped into this problem after the latest xserver update.
>=20

Me too.

> Previously my MS Intellimouse Optical worked perfectly:=20
>=20

I've got the same mouse, same thing here.

> After the upgrade, wheel and thumb buttons stopped working, and I got t=
he wheel
> working by commenting out following lines in xorg.conf, thus resorting
> to their new
> default values:
>=20
> # Option "Buttons" "7"
> # Option "ZAxisMapping" "6 7"
>=20
> Can you please give instructions for getting also the thumb buttons to
> work again? I don't understand how that ZAxisMapping thing is supposed
> to work with my mouse.
>=20

I've described the problem here :
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D345704

You can have your 5 first buttons working (so it includes the wheel).

Let: Option "Buttons" "7"
Set: Option "ZAxisMapping" "4 5"

And you are done.

You can also deactivate your xmodmap which should be pointer =3D 1 2 3 6 =
7 4 5
As described in my bugreport, X see 11 buttons on this mouse (that's the
main problem), xmodmap expects 11 buttons to be mapped, not 7.

If you also want to use your 2 specials left and right buttons, for all
I know, it's not actually possible.

--=20
Alexandre Ahmim-Richard
passe at clope dot net
http://www.u-admin.org

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Tue, 3 Jan 2006 17:42:35 -0500
From: Christopher Martin <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: Re: 097_mouse_zaxis_mapping_pushes_up_buttons should be dropped as of 6.9/7.0 RC3

severity 343728 grave
stop

Since this patch is still included in the X.Org packaging in unstable,
imwheel is now broken. Please drop the patch (made obsolete by upstream
changes, as explained below) in the next upload.

This link (and the links it contains) explains further:
https://bugs.freedesktop.org/show_bug.cgi?id=1900

Thanks,
Christopher Martin

On Saturday 17 December 2005 12:14, Christopher Martin wrote:
> Package: xserver-xorg
> Version: 6.8.99.903.dfsg.1-1
> Severity: normal
> Tags: experimental
>
> Debian's X.Org packaging includes the patch
> 097_mouse_zaxis_mapping_pushes_up_buttons.diff, which serves to adjust
> mouse button mappings so that users didn't have to use xmodmap to make
> all available physical buttons available for use.
>
> In X.Org 6.9/7.0 RC3, upstream made changes to the mouse button handling.
> The default ZAxisMapping is "4 5 6 7", accommodating scroll wheels with
> two axes. Also by default the mouse physical : logical button mapping is
> now "1 2 3 8 9 ...", so that all physical buttons can be used (thumb
> buttons are 8 and 9) without conflict with the scroll wheel.
>
> These changes make Debian's 097 patch obsolete, since now all buttons are
> properly exposed by default. Indeed, continuing to include the 097 patch
> causes problems, since the buttons are shifted around twice, and it all
> becomes very messy. (When wondering why imwheel stopped working with the
> latest experimental X, I read up on upstream's changes, and had to
> rebuild X without 097 to get the expected new behaviour).
>
> FYI, since you'll probably get questions/bug reports, this change in
> behaviour has other implications. Mozilla uses buttons 6 and 7 for
> "forward" and "back", but this doesn't work anymore, since those buttons
> are now assumed to represent the horizontal axis of the scroll wheel,
> whether your mouse has one or not. Users can of course use xmodmap or the
> new ButtonMapping xorg.conf option to work around this. As far as I can
> tell, Qt applications seem to use 6 and 7 for horizontal scrolling
> already, so they shouldn't generate too many reports of brokenness.
>
> Cheers,
> Christopher Martin
>
> I'd also like to append this obligatory nag to have bug #237877 looked at
> :)

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Tue, 3 Jan 2006 18:23:04 -0500
From: Christopher Martin <email address hidden>
To: <email address hidden>
Subject: Re: 097_mouse_zaxis_mapping_pushes_up_buttons should be dropped as of 6.9/7.0 RC3

tags 343728 - experimental
stop

Now in unstable.

On Tuesday 03 January 2006 17:42, Christopher Martin wrote:
> severity 343728 grave
> stop
>
> Since this patch is still included in the X.Org packaging in unstable,
> imwheel is now broken. Please drop the patch (made obsolete by upstream
> changes, as explained below) in the next upload.
>
> This link (and the links it contains) explains further:
> https://bugs.freedesktop.org/show_bug.cgi?id=1900
>
> Thanks,
> Christopher Martin

Revision history for this message
In , David Nusinow (david-nusinow-verizon) wrote : Setting severity

severity 343728 normal
thanks

Revision history for this message
In , David Nusinow (david-nusinow-verizon) wrote : Tag Pending Bugs

tags 345328 +pending
tags 343693 +pending
tags 343822 +pending
tags 345285 +pending
tags 345406 +pending
tags 345446 +pending
tags 345387 +pending
tags 343728 +pending
tags 345893 +pending
thanks

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-id: <20060104221329.GE12894@localdomain>
Date: Wed, 04 Jan 2006 17:13:29 -0500
From: David Nusinow <email address hidden>
To: <email address hidden>
Subject: Setting severity

severity 343728 normal
thanks

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-id: <20060104222931.GF12894@localdomain>
Date: Wed, 04 Jan 2006 17:29:31 -0500
From: David Nusinow <email address hidden>
To: <email address hidden>
Subject: Tag Pending Bugs

tags 345328 +pending
tags 343693 +pending
tags 343822 +pending
tags 345285 +pending
tags 345406 +pending
tags 345446 +pending
tags 345387 +pending
tags 343728 +pending
tags 345893 +pending
thanks

Revision history for this message
Daniel Stone (daniels) wrote :

hrngh

Revision history for this message
In , David Nusinow (dnusinow) wrote : Bug#343728: fixed in xorg-x11 6.9.0.dfsg.1-2
Download full text (43.3 KiB)

Source: xorg-x11
Source-Version: 6.9.0.dfsg.1-2

We believe that the bug you reported is fixed in the latest version of
xorg-x11, which is due to be installed in the Debian FTP archive:

lbxproxy_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/lbxproxy_6.9.0.dfsg.1-2_i386.deb
libdmx-dev_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libdmx-dev_6.9.0.dfsg.1-2_i386.deb
libdmx1-dbg_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libdmx1-dbg_6.9.0.dfsg.1-2_i386.deb
libdmx1_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libdmx1_6.9.0.dfsg.1-2_i386.deb
libfs-dev_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libfs-dev_6.9.0.dfsg.1-2_i386.deb
libfs6-dbg_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libfs6-dbg_6.9.0.dfsg.1-2_i386.deb
libfs6_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libfs6_6.9.0.dfsg.1-2_i386.deb
libglu1-xorg-dbg_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libglu1-xorg-dbg_6.9.0.dfsg.1-2_i386.deb
libglu1-xorg-dev_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libglu1-xorg-dev_6.9.0.dfsg.1-2_i386.deb
libglu1-xorg_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libglu1-xorg_6.9.0.dfsg.1-2_i386.deb
libice-dev_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libice-dev_6.9.0.dfsg.1-2_i386.deb
libice6-dbg_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libice6-dbg_6.9.0.dfsg.1-2_i386.deb
libice6_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libice6_6.9.0.dfsg.1-2_i386.deb
libsm-dev_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libsm-dev_6.9.0.dfsg.1-2_i386.deb
libsm6-dbg_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libsm6-dbg_6.9.0.dfsg.1-2_i386.deb
libsm6_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libsm6_6.9.0.dfsg.1-2_i386.deb
libx11-6-dbg_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libx11-6-dbg_6.9.0.dfsg.1-2_i386.deb
libx11-6_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libx11-6_6.9.0.dfsg.1-2_i386.deb
libx11-dev_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libx11-dev_6.9.0.dfsg.1-2_i386.deb
libxau-dev_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libxau-dev_6.9.0.dfsg.1-2_i386.deb
libxau6-dbg_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libxau6-dbg_6.9.0.dfsg.1-2_i386.deb
libxau6_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libxau6_6.9.0.dfsg.1-2_i386.deb
libxaw6-dbg_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libxaw6-dbg_6.9.0.dfsg.1-2_i386.deb
libxaw6-dev_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libxaw6-dev_6.9.0.dfsg.1-2_i386.deb
libxaw6_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libxaw6_6.9.0.dfsg.1-2_i386.deb
libxaw7-dbg_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libxaw7-dbg_6.9.0.dfsg.1-2_i386.deb
libxaw7-dev_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libxaw7-dev_6.9.0.dfsg.1-2_i386.deb
libxaw7_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libxaw7_6.9.0.dfsg.1-2_i386.deb
libxaw8-dbg_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libxaw8-dbg_6.9.0.dfsg.1-2_i386.deb
libxaw8-dev_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libxaw8-dev_6.9.0.dfsg.1-2_i386.deb
libxaw8_6.9.0.dfsg.1-2_i386.deb
  to pool/main/x/xorg-x11/libxaw8_6.9.0.dfsg.1-2_i386.deb
libxcomposite-dev_6.9.0.dfsg.1-2_i386.deb
  to pool...

Revision history for this message
In , charlene Lachawiec (charlene-lachawiec) wrote : Mission Bios

He moved around the fence to the sagging gate and went into the plot.

AN ALLE FINANZINVESTOREN!
DIESE AKTIE WIRD DURCHSTARTEN!
FREITAG 20. APRIL STARTET DIE HAUSSE!
REALISIERTER KURSGEWINN VON 400%+ IN 5 TAGEN!

Symbol: G7Q.F
Company: COUNTY LINE ENERGY
5 Tages Kursziel: 0.95
Schlusskurs: 0.21
WKN: A0J3B0
ISIN: US2224791077
Markt: Frankfurt

LASSEN SIE SICH DIESE CHANCE NICHT ENTGEHEN!
G7Q WIRD WIE EINE RAKETE DURCHSTARTEN!
UNSERE ERWARTUNGEN WIRD G7Q.F UBERTREFFEN!

The dry heat seemed even worse outside, for all the sun still sat on the canvas wall around the menagerie.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.