Re: hid-logitech-hidpp / hid-logitech-dj driver hiding inputs and breaking Logitech G700s buttons

[Hamza Attak <hamza@attak.fr>]

Hi Filipe,

I'm on the latest 5.4.3 from kernel from kernel.org git repository. Only
a few security options are tweaked in the kconfig.
For your information, I am also facing the same issue on untouched 
Ubuntu
built kernels,

I never followed linux-input before and don't know how active was the 
code
taking care of the G700s, but do you think there might have been a 
regression
since you say that it was a fixed issue?

Unfortunately, I didn't keep track on when it happened, ie after a 
kernel
upgrade or if it was always there and I only noticed after trying the 
mouse
wirelessly.

Thanks,
Hamza ATTAK.


On Mon, 16 Dec, 2019 at 12:49 AM, Filipe Laíns <lains@archlinux.org> 
wrote:
> On Sun, 2019-12-15 at 19:34 +0000, Hamza Attak wrote:
>>  Hi,
>> 
>>  I have been facing an issue with my Logitech G700s mouse on wireless
>>  (id of
>>  the receiver is 046d:c531).
>>  Most of the buttons are not working, namely:
>>   G6, G7, G8, G9, G10
>> 
>>  My testing has shown that when pressing these buttons, no input at
>>  all
>>  is
>>  showing on both interfaces:
>>   /dev/input/by-id/usb-Logitech_USB_Receiver-if01-event-mouse
>>   /dev/input/by-id/usb-Logitech_USB_Receiver-if01-mouse
>> 
>>  Further testing shown that having 'hid_logitech_dj' or
>>  'hid_logitech_hidpp'
>>  module loaded is causing the issue, just one of them loaded is
>>  enough
>>  to create
>>  the issue. This led me to contact you by looking at
>>  'drivers/hid/hid-logitech-dj.c' and 'drivers/hid/hid-logitech-
>>  hidpp.c').
>>  rmmod'ing the modules and using 'usbhid' module alone is solving the
>>  issue, as
>>  Linux is now receiving correct input from the buttons.
>> 
>>  Blacklisting the modules would do the trick for wireless on my local
>>  system, but
>>  it doesn't seem right no to report this bug for others.
>> 
>>  For info, it works perfectly wired, so I guess the issue might be
>>  with
>>  the dj
>>  receiver code.
>> 
>>  Before thinking of modifying the code myself, I am sending you this
>>  message and
>>  see what would be a clean fix for the issue.
>> 
>>  Thanks,
>>  Hamza ATTAK.
>> 
> 
> Hello Hamza,
> 
> Which kernel version are you using? I am pretty sure this is an issue
> that was fixed in newer versions.
> 
> Thank you,
> Filipe Laíns