Logitech G300 Mouse left mouse click broken

[James Jenner]

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.

Refer to http://ubuntuforums.org/showpost.php?p=11424355&postcount=8 for the workaround identified by qrazi.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: xinput 1.5.3-2ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 280.13 Wed Jul 27 16:53:56 PDT 2011
 GCC version: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3)
.tmp.unity.support.test.0:

ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,move,resize,imgpng,gnomecompat,grid,regex,snap,animation,place,workarounds,vpswitch,mousepoll,session,expo,ezoom,staticswitcher,wall,fade,scale,unityshell]
CompositorRunning: compiz
Date: Mon Nov 7 21:23:43 2011
DistUpgraded: Log time: 2011-10-29 15:38:32.700157
DistroCodename: oneiric
DistroVariant: ubuntu
DkmsStatus:
 nvidia-current, 280.13, 2.6.38-11-generic, x86_64: installed
 nvidia-current, 280.13, 3.0.0-12-generic, x86_64: installed
 nvidia-current-updates, 280.13, 3.0.0-12-generic, x86_64: installed
 vboxhost, 4.1.4, 2.6.38-11-generic, x86_64: installed
 vboxhost, 4.1.4, 3.0.0-12-generic, x86_64: installed
GraphicsCard:
 nVidia Corporation GF106 [GeForce 450 GTS] [10de:0dc4] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8365]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
JockeyStatus:
 xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Disabled, Not in use)
 xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Enabled, In use)
MachineType: System manufacturer System Product Name
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=4d8b6a18-7378-470c-8fb9-339a5d560d5c ro quiet splash vt.handoff=7
SourcePackage: xinput
UpgradeStatus: Upgraded to oneiric on 2011-10-29 (9 days ago)
dmi.bios.date: 06/27/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1850
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8P67
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1850:bd06/27/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8P67:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu5
version.ia32-libs: ia32-libs 20090808ubuntu26
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1

[Tomáš Myšík (gapon)]

One note: It seems that this mouse works correctly on Fedora where the "keyboard part" of this mouse is _enabled_.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[James Jenner (james-g-jenner)]

I have discovered over time that the workaround I have posted is not that effective, as the id can change depending on what usb devices are connected at (i presume) boot time.

As such I have found the following command to be far more effective, well it works on my system anyway.

xinput set-prop "keyboard:Logitech Gaming Mouse G300" 121 0

I'm not certain if the property id can change, but I've noticed that for me it has always been 121. It's just the device I that has changed. using the name works around this issue. Effectively, the above command as a startup is a workable workaround.

[Edward Pienkowski (mrpienk)]

The property id can change. However, you can use a few commands to detect which property you need to change. Here's how I did it on my desktop:

Computer@User:~$ xinput list | grep G300
    ↳ Logitech Gaming Mouse G300 id=8 [slave pointer (2)]
    ↳ Logitech Gaming Mouse G300 id=9 [slave keyboard (3)]

Notice the device ID for a keyboard is included. You'll want to use that ID in the next command.

edward@Odin:~$ xinput list-props 9
Device 'Logitech Gaming Mouse G300':
 Device Enabled (142): 1

Other Stuff that isn't important to us right now will also be printed. Let's focus on the Device Enabled (142) line. It's set to 1, but we want it set to 0. To do that, we issue the following command using the two numbers (9 & 142) that we gathered from the previous commands:

xinput set-prop 9 142 0

This sets the value of 142 within device 9 to 0. Your first two numbers might be different, but you need the 0 to make sure to turn the keyboard functionality of the device off so it functions purely as a mouse.

[Cyril Raphanel (cyril-raphanel)]

Any hope to get the keyboard function actually working?
It would be also great if we could configure it under linux ....

[Patrik B. (inoki-deactivatedaccount)]

Issue still present in 14.04.3.