After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 499471 - mouse buttons 8 and 9 behave like button 1
mouse buttons 8 and 9 behave like button 1
Status: RESOLVED INCOMPLETE
Product: gtk+
Classification: Platform
Component: Class: GdkDevice
unspecified
Other All
: Normal minor
: ---
Assigned To: gtk-bugs
Carlos Garnacho
Depends on:
Blocks:
 
 
Reported: 2007-11-25 02:29 UTC by rwxr-xr-x
Modified: 2012-02-07 22:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description rwxr-xr-x 2007-11-25 02:29:08 UTC
Please describe the problem:
I have a mouse with 11 buttons (2 of which don't seem to be recognized at all). xev shows button presses for the three main buttons, the scroll wheel (4 and 5), horizontal scrolling (6 and 7), and two other buttons (8 and 9). However, buttons 8 and 9 act like button 1 in firefox and gimp (that's why I think it's a Gtk+ bug), i.e. they can be used to click on buttons, drag selections, etc.

Oh, wait. That description only applies to firefox. In gimp, buttons 8 and 9 can be used in the menu bar, but clicking on buttons (like OK or Cancel) only gives them a dotted "selected" look (it doesn't actually activate them); and you can't draw a line with them (or use any other tools).

But in firefox buttons 1, 8 and 9 are completely interchangeable. You can even press button 8, mark some text, then press-and-release button 1 (or 9) and the selection stops, even though button 8 is still held down (releasing it later has no effect).

Steps to reproduce:
1. start firefox or gimp
2. move mouse pointer over File menu bar entry
3. click mouse button 8 or 9


Actual results:
the File menu activates

Expected results:
nothing happens

Does this happen every time?
yes

Other information:
Comment 1 André Klapper 2009-11-08 14:17:12 UTC
So why do you think is this a GTK issue?
Comment 2 André Klapper 2012-01-06 15:40:45 UTC
Is this still an issue? If so, which distribution and gtk+ version do you use nowadays? How is the behavior in another GNOME application, like Gedit?
Comment 3 André Klapper 2012-02-07 22:37:40 UTC
Hi rwxr-xr-x, 
I am closing this bug report as no updated information has been provided.
Please feel free to reopen this bug if you can provide the information that was asked for in a previous comment.