My mouse is Razer Diamondback 3G. It has 9 buttons (3 on top, 2 on every side, rolling the mouse wheel is 2 "buttons" - makes 9). Interestingly, Xorg.0.log insists that it finds 11 buttons on this mouse (interestingly, this guy has 7 on 1.6.0: http://linuxoutlaws.com/forums/viewtopic.php?p=42883#p42883 ). But even though it says it sees 11 buttons out of physical 9, only 7 work, with buttons 6-7 reporting 4-5 (or maybe 5-4 in this case). So I have buttons 1-2-3 reporting normal, mouse whell is buttons 4 and 5, the right-side buttons are also 4 and 5 (and can be used to scroll windows), the left-side buttons are 9 and 8. What can I do about it? Here's relevant info from Xorg.0.log. I don't define any mouse in xorg.conf, the ConstantDeceleration option I've defined in /etc/hal/fdi/policy/10-x11-input.fdi, everything else is probed/default if I understand correctly. (II) config/hal: Adding input device Razer Razer Diamondback 3G (**) Razer Razer Diamondback 3G: always reports core events (**) Razer Razer Diamondback 3G: Device: "/dev/input/event4" (II) Razer Razer Diamondback 3G: Found 11 mouse buttons (II) Razer Razer Diamondback 3G: Found scroll wheel(s) (II) Razer Razer Diamondback 3G: Found relative axes (II) Razer Razer Diamondback 3G: Found x and y relative axes (II) Razer Razer Diamondback 3G: Configuring as mouse (**) Razer Razer Diamondback 3G: YAxisMapping: buttons 4 and 5 (**) Razer Razer Diamondback 3G: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 (II) XINPUT: Adding extended input device "Razer Razer Diamondback 3G" (type: MOUSE) (**) Razer Razer Diamondback 3G: (accel) keeping acceleration scheme 1 (**) Option "ConstantDeceleration" "2" (**) Razer Razer Diamondback 3G: (accel) constant deceleration by 2.0 (**) Razer Razer Diamondback 3G: (accel) acceleration profile 0 (II) Razer Razer Diamondback 3G: initialized for relative axes.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf, if available), any /etc/hal/fdi/policy files, output of the dmesg command, system log (/var/log/messages), and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. Take a look also on https://fedoraproject.org/wiki/Xorg/Input_Triage_Algorithm to find out which other sources of information can be useful for anaylsis of your issue. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 397156 [details] xorg.conf
Created attachment 397158 [details] /etc/hal/fdi/policy/10-x11-input.fdi for ConstantDeceleration
Created attachment 397161 [details] dmesg
Created attachment 397162 [details] Xorg.0.log
I've attached relevant files. /var/log/messages is 99% spam from named and the rest is already in the dmesg. If you feel using the nVidia drivers can spoil my system to the point of making 2 of 9 mouse buttons broken leaving everything else working, I can remove it and have an untainted dmesg+Xorg.0.log, but I really hope you don't mind. My xorg.conf is basically needed to force correct HorizSync/VertRefresh for my monitor and proper ModeLines, the mouse config is completely removed now (everything done through HAL).
Please run evtest against the device and press all the buttons, this should tell us why evdev detects too many mouse buttons and whether the mapping is screwed up in the kernel. Thanks
Created attachment 398663 [details] evtest output Pressed buttons: - wheel up, down (not technically buttons) - top buttons: left, middle, right - left buttons: head, rear - right buttons: head, rear (these get registered as whell up/down) Please note SideBtn and ExtraBtn - those would be the buttons that pretend to be a wheel (I've already mentioned left buttons have higher numbers, plus the left ones actually do work as back/forward in web browsers).
right, so the reason why evdev claims 11 buttons is because it sees Left Middle Right and those four: Event code 275 (SideBtn) Event code 276 (ExtraBtn) Event code 277 (ForwardBtn) Event code 278 (BackBtn) for legacy reasons, buttons 4-7 are for scrolling so a mouse with LMR and extra buttons has buttons 1-7 + those extra buttons - 11 in your case. now, the issue in your case is that this particular mouse claims that it has forward and back buttons but doesn't send the events - instead it sends the wheel events. this is either a kernel or hardware issue, reassigning to the kernel.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Nothing changed in this matter, still present in F14.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping