Red Hat Bugzilla – Bug 760437
Mouse Logitech G300 compability
Last modified: 2013-04-29 03:54:16 EDT
Description of problem:
The Logitech G300 mouse is a gaming mouse that includes programmable buttons. When first installed it is recognised and appears to work. However the left mouse click appears to move the mouse to the top left hand corner of the screen and perform a drag operation. Multiple left mouse clicks causes unexpected behaviour. This also affects drag actions with the left mouse button.
Using xinput list, the mouse is reported under Virtual core keyboard. Disabling the G300 as a keyboard input fixes the problem and the mouse behaves correctly.
Version-Release number of selected component (if applicable):
Every time after connect mouse Logitech G300 to Fedora 16. The mouse is totally unusable.
Steps to Reproduce:
1. Connect mouse to F16
2. Verify pointer/click behavior with KDE or Gnome.
Unexpected mouse pointer behavior
As mouse is intended
I tried Logitech G300 mouse with latest distro Arch linux + Gnome, and got the same problem.
There is only workaround exist:
This bug should be fixed with patch:
Force x/y axes to exist on devices with any other axes (#44655)
I will able to check as soon as patch is pushed/released for FC16.
xorg-x11-drv-evdev-220.127.116.111-5.20120118git9d9c9870c.fc16 has been submitted as an update for Fedora 16.
With this release my issue with Logitech G300 is fixed and it is working properly.
xorg-x11-drv-evdev-18.104.22.1681-7.20120118git9d9c9870c.fc16 has been submitted as an update for Fedora 16.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing xorg-x11-drv-evdev-22.214.171.1241-7.20120118git9d9c9870c.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
xorg-x11-drv-evdev-126.96.36.1991-7.20120118git9d9c9870c.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.