Logitech G300s Mouse doesn't click

Support
1

Hello everyone,
I have a Logitech G300S mouse, that the system recognizes but it won’t recognize clicks. I am able to move the cursor freely, but all buttons do not respond.

I read this link - https://wiki.archlinux.org/title/Logitech_G300 but it didn’t help.

Output from xinput:

 ~ xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ SYNA7501:00 06CB:16C9                   	id=15	[slave  pointer  (2)]
⎜   ↳ ETPS/2 Elantech Touchpad                	id=18	[slave  pointer  (2)]
⎜   ↳ Logitech G300s Optical Gaming Mouse     	id=13	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Power Button                            	id=8	[slave  keyboard (3)]
    ↳ Dell KB216 Wired Keyboard               	id=9	[slave  keyboard (3)]
    ↳ Dell KB216 Wired Keyboard System Control	id=10	[slave  keyboard (3)]
    ↳ Dell KB216 Wired Keyboard Consumer Control	id=11	[slave  keyboard (3)]
    ↳ EasyCamera: EasyCamera                  	id=14	[slave  keyboard (3)]
    ↳ Ideapad extra buttons                   	id=16	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=17	[slave  keyboard (3)]
    ↳ Logitech G300s Optical Gaming Mouse Keyboard	id=12	[slave  keyboard (3)]

A note:
I don’t posses a Logitech keyboard (it’s by Dell), but for some reason it shows “Gaming Mouse Keyboard”.

Does someone have an idea?
Thanks in advance!

2

yes disable the keyboard and FOLLOW the instructions in the archwiki as described !!!

We have to disable the G300 keyboard to make it work correctly as follows:

#!/bin/sh
DEVICE_ID=$(xinput list |  grep "Logitech Gaming Mouse G300" | grep keyboard | sed 's/.*id=\([0-9]*\).*/\1/')

if xinput -list-props $DEVICE_ID | grep "Device Enabled" | grep "1$" > /dev/null
then
        xinput set-int-prop $DEVICE_ID "Device Enabled" 8 0
fi

Make this executable and run it to see if everything is working. You can also put it into your xinitrc.d to make it load automatically.

Another shorter version:
3

Thanks for the reply!
I did cancel the key board:

 ~ xinput -list-props 13
Device 'Logitech G300s Optical Gaming Mouse Keyboard':
	Device Enabled (179):	0
	Coordinate Transformation Matrix (181):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	libinput Send Events Modes Available (292):	1, 0
	libinput Send Events Mode Enabled (293):	0, 0
	libinput Send Events Mode Enabled Default (294):	0, 0
	Device Node (295):	"/dev/input/event20"
	Device Product ID (296):	1133, 49734
4

so then go on and install the aur-package as described in the wiki

5

You’ve probably figured this out by now. It’s a composite device, a mouse and a keyboard, because it’s a programmable mouse. If you disable the keyboard you won’t be able to bind keyboard keys or combos.

The above script works as intended but it also disables the buttons, since we disabled the keyboard function of the G300. To make this mouse working as a mouse and being able to use the buttons, we can use ratslapAUR for customization (colors and buttons). - Archwiki linked above.

If that’s correct then the mouse is sending keyboard keys instead of mouse buttons. Maybe you just need to configure it correctly instead of disabling the keyboard, having said that the mouse should already be configured properly. Alas I don’t have one to test.

If you click on your link it takes you to https://archwiki/ which is invalid.