Bug 218094
| Summary: | Logitech G915 Wireless Keyboard acts weird on 6.6.0 | ||
|---|---|---|---|
| Product: | Linux | Reporter: | LinuxCat (masch77.linuxcat) |
| Component: | Kernel | Assignee: | Virtual assignee for kernel bugs (linux-kernel) |
| Status: | RESOLVED CODE_FIX | ||
| Severity: | normal | CC: | arthurborsboom, bagasdotme, darkstego, etienne.blanchet, felix.fourcolor, kozinov, mario.georgiev, misc, mmbossoni, pori.ilari, psi-jack, scott.silverman, stefmitropoulos, t.clastres, tiwai |
| Priority: | P3 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | Subsystem: | ||
| Regression: | No | Bisected commit-id: | |
| Attachments: | dmesg with call trace logitech g15 | ||
|
Description
LinuxCat
2023-11-01 08:25:53 UTC
Video was not included because it was too big - here it is : https://streamable.com/ac6l8u Bisected to 9d1bd9346241cd6963b58da7ffb7ed303285f684 is the first bad commit commit 9d1bd9346241cd6963b58da7ffb7ed303285f684 Author: Mavroudis Chatzilazaridis <mavchatz@protonmail.com> Date: Sun Jul 16 18:23:44 2023 +0000 HID: logitech-dj: Add support for a new lightspeed receiver iteration The lightspeed receiver for the Pro X Superlight uses 13 byte mouse reports without a report id. The workaround for such cases has been adjusted to handle these larger packets. The device now reports the status of its battery in wireless mode and libratbag now recognizes the device and it can be configured with Piper. https://github.com/libratbag/libratbag/pull/1122 Co-developed-by: Filipe Laíns <lains@riseup.net> Signed-off-by: Filipe Laíns <lains@riseup.net> Signed-off-by: Mavroudis Chatzilazaridis <mavchatz@protonmail.com> Reviewed-by: Bastien Nocera <hadess@hadess.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz> drivers/hid/hid-ids.h | 1 + drivers/hid/hid-logitech-dj.c | 11 ++++++++--- 2 files changed, 9 insertions(+), 3 deletions(-) (In reply to LinuxCat from comment #0) > Hello, > After upgrading from 6.5.9 to 6.6.0, my keyboard started acting really weird > in its wireless mode, key actions sent are completely wrong, see video > attached. > > Most keys are perceived as either E, 3 or F7, with F8 and <, as well. > > Modifier keys (CTRL, ALT, ALT GR, Shift and Super) are working normally, as > well as media control keys (pause/play, previous, next, mute and sound > up/down). > > The keyboard works as expected if it's wired. You may follow troubleshooting guide from Ubuntu [1]. But instead of reporting findings to Launchpad tracker, report them here. [1]: https://wiki.ubuntu.com/Hotkeys/Troubleshooting (In reply to Bagas Sanjaya from comment #3) > > You may follow troubleshooting guide from Ubuntu [1]. But instead of > reporting findings to Launchpad tracker, report them here. > > [1]: https://wiki.ubuntu.com/Hotkeys/Troubleshooting Hello, I probably should have precised it but I'm using Arch (CachyOS) and KDE Plasma. Regardless, I could follow the evtest part. When I press the o key : Event: time 1698958075.926178, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70040 Event: time 1698958075.926178, type 1 (EV_KEY), code 65 (KEY_F7), value 1 Event: time 1698958075.926178, -------------- SYN_REPORT ------------ Event: time 1698958075.976187, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70040 Event: time 1698958075.976187, type 1 (EV_KEY), code 65 (KEY_F7), value 0 Event: time 1698958075.976187, -------------- SYN_REPORT ------------ When I press the g key : Event: time 1698958076.416549, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70040 Event: time 1698958076.416549, type 1 (EV_KEY), code 65 (KEY_F7), value 1 Event: time 1698958076.416549, -------------- SYN_REPORT ------------ Event: time 1698958076.465476, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70040 Event: time 1698958076.465476, type 1 (EV_KEY), code 65 (KEY_F7), value 0 Event: time 1698958076.465476, -------------- SYN_REPORT ------------ When I press the backspace key : Event: time 1698958077.317214, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70040 Event: time 1698958077.317214, type 1 (EV_KEY), code 65 (KEY_F7), value 1 Event: time 1698958077.317214, -------------- SYN_REPORT ------------ Event: time 1698958077.352191, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70040 Event: time 1698958077.352191, type 1 (EV_KEY), code 65 (KEY_F7), value 0 Event: time 1698958077.352191, -------------- SYN_REPORT ------------ There doesn't seem to be any difference here. The problem probably comes from the commit mentioned by Marcelo, because this keyboard also uses a lightspeed receiver. I have the same keyboard, Logitech G915 Wireless, and I'm also facing this same problem using CachyOS Kernel 6.6.1 on Fedora 39 while using it on Wireless mode. Like mentioned previously, it works fine in wired mode. Possibly related: Logitech G510s keyboard not working on kernel 6.6.1. [ 7.990759] sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:08.0/0000:07:00.0/0000:08:0c.0/0000:0c:00.0/usb1/1-3/1-3:1.1/0003:046D:C22D.000B/leds/g15::kbd_backlight/color' [ 7.990762] CPU: 4 PID: 451 Comm: (udev-worker) Tainted: G OE 6.6.1-arch1-1 #1 be166a630cd909acf8820643140e9106c6ea80e6 [ 7.990766] Hardware name: ASUS System Product Name/TUF GAMING X670E-PLUS WIFI, BIOS 1813 10/13/2023 [ 7.990767] Call Trace: [ 7.990769] <TASK> [ 7.990771] dump_stack_lvl+0x47/0x60 [ 7.990778] sysfs_warn_dup+0x5a/0x70 [ 7.990783] sysfs_add_file_mode_ns+0x11a/0x130 [ 7.990786] internal_create_group+0x125/0x3b0 [ 7.990789] internal_create_groups+0x42/0xa0 [ 7.990791] device_add+0x5ad/0x8a0 [ 7.990794] ? srso_alias_return_thunk+0x5/0x7f [ 7.990798] ? kstrdup+0x4c/0x70 [ 7.990802] device_create_groups_vargs+0xce/0xf0 [ 7.990805] device_create_with_groups+0x4b/0x70 [ 7.990808] led_classdev_register_ext+0x1d2/0x470 [ 7.990812] ? devm_led_classdev_register_ext+0x3a/0x90 [ 7.990817] devm_led_classdev_register_ext+0x50/0x90 [ 7.990820] lg_g15_probe+0x667/0x770 [hid_lg_g15 4a43fb61ec72c8e966287bea16924535918cb678] [ 7.990826] hid_device_probe+0x10e/0x1a0 [ 7.990829] really_probe+0x19b/0x3e0 [ 7.990833] ? __pfx___device_attach_driver+0x10/0x10 [ 7.990835] __driver_probe_device+0x78/0x160 [ 7.990838] driver_probe_device+0x1f/0x90 [ 7.990841] __device_attach_driver+0x89/0x110 [ 7.990844] bus_for_each_drv+0x92/0xf0 [ 7.990847] __device_attach+0xb2/0x1b0 [ 7.990850] ? __pfx___hid_bus_reprobe_drivers+0x10/0x10 [ 7.990853] device_reprobe+0x4e/0x90 [ 7.990855] ? __hid_bus_reprobe_drivers+0x39/0x60 [ 7.990857] bus_for_each_dev+0x85/0xd0 [ 7.990860] ? __pfx___hid_bus_driver_added+0x10/0x10 [ 7.990862] __hid_bus_driver_added+0x2c/0x40 [ 7.990865] bus_for_each_drv+0x92/0xf0 [ 7.990868] __hid_register_driver+0x74/0x80 [ 7.990871] ? __pfx_ms_driver_init+0x10/0x10 [hid_microsoft a9a7eb35e2e5d1c3f68fd046c8c3a94730fe7fdb] [ 7.990876] do_one_initcall+0x5a/0x320 [ 7.990883] do_init_module+0x60/0x240 [ 7.990888] init_module_from_file+0x89/0xe0 [ 7.990894] idempotent_init_module+0x120/0x2b0 [ 7.990898] __x64_sys_finit_module+0x5e/0xb0 [ 7.990901] do_syscall_64+0x5d/0x90 [ 7.990904] ? do_syscall_64+0x6c/0x90 [ 7.990906] ? srso_alias_return_thunk+0x5/0x7f [ 7.990908] ? exit_to_user_mode_prepare+0x132/0x1f0 [ 7.990911] ? srso_alias_return_thunk+0x5/0x7f [ 7.990914] ? syscall_exit_to_user_mode+0x2b/0x40 [ 7.990916] ? srso_alias_return_thunk+0x5/0x7f [ 7.990918] ? do_syscall_64+0x6c/0x90 [ 7.990920] ? syscall_exit_to_user_mode+0x2b/0x40 [ 7.990922] ? srso_alias_return_thunk+0x5/0x7f [ 7.990924] ? do_syscall_64+0x6c/0x90 [ 7.990927] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 7.990930] RIP: 0033:0x7f4ef790773d [ 7.990947] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 95 0c 00 f7 d8 64 89 01 48 [ 7.990948] RSP: 002b:00007ffe65533e38 EFLAGS: 00000246 ORIG_RAX: 0000000000000139 [ 7.990951] RAX: ffffffffffffffda RBX: 000056078c53f520 RCX: 00007f4ef790773d [ 7.990952] RDX: 0000000000000004 RSI: 00007f4ef7e05376 RDI: 000000000000000e [ 7.990953] RBP: 00007f4ef7e05376 R08: 00005602ec2c7357 R09: fffffffffffffe90 [ 7.990954] R10: 0000000000000050 R11: 0000000000000246 R12: 0000000000020000 [ 7.990956] R13: 000056078c52e2f0 R14: 0000000000000000 R15: 000056078c527640 [ 7.990960] </TASK> Created attachment 305384 [details]
dmesg with call trace logitech g15
Same behavior here with G915 Wireless and Kernels 6.6.0 and 6.6.1. Was working fine in branch 6.5.x and olders. Confirming for Logitech G510s keyboard: - kernel 6.5.9 works - kernel 6.6.1 broken I have a logitech g915 tkl. 6.1 (arch) works for me. (In reply to felix.fourcolor from comment #10) > I have a logitech g915 tkl. 6.1 (arch) works for me. I mean 6.6.1 I have the same issue with the lightspeed receiver. I have both my G915 TKL and G502X connected to it and they both don't work as they were on the 6.5.x kernel. I'm on Arch as well. They work correctly only when connected through USB directly. I just upgraded to 6.6.1 and can confirm the problem is still present. Why does it work for me then? (In reply to felix.fourcolor from comment #14) > Why does it work for me then? Are you using the keyboard while plugged in? I can confirm that on 6.6.1 (arch) the issue is present when using the keyboard wirelessly. The keyboard behaves normally if connected wired. On 6.5.9 (arch) the keyboard behaves normally, both wired and wireless. I use the usb receiver. Everything is fine. Unless you mean it's the bluetooth that's broken? Then I don't know, I never tried. (In reply to felix.fourcolor from comment #16) > I use the usb receiver. Everything is fine. > > Unless you mean it's the bluetooth that's broken? Then I don't know, I never > tried. (In reply to felix.fourcolor from comment #10) > I have a logitech g915 tkl. 6.1 (arch) works for me. Do you mean "6.6.1" and not "6.1"? 6.1 works just fine, it's only 6.6.1 (and I believe 6.6.0 as well) that have the issue. I meant 6.6.1. I did correct it in the comment right after. (In reply to felix.fourcolor from comment #18) > I meant 6.6.1. I did correct it in the comment right after. Maybe you have a different version of the receiver? Mine reports as: Path : /dev/hidraw7 USB ID : 046d:C547 Serial : Firmware : 04.02.B0009 Bootloader : 02.09 Other : B8.15 Notifications: wireless software present > Maybe you have a different version of the receiver?
Excuse my ignorance, how do I access that information?
Mine shows as:
Path : /dev/hidraw10
USB ID : 046d:C547
Serial : 15031480
Firmware : 04.02.B0009
Bootloader : 02.09
Other : 70.7E
Notifications: wireless
software present
That information is from Solaar.
Here's mine. Everything works.
Path : /dev/hidraw2
USB ID : 046d:C545
Serial : 2B2E40F0
Firmware : 02.01.B0006
Bootloader : 00.01
Other : 18.F6
Notifications: wireless
software present
In the linux-hardware.org DB the C545 and C547 are mostly the same. The only difference I see is the type. C545 have "input/keyboard" and c547 is "input/mouse". Probably is not marked correctly just on this DB. https://linux-hardware.org/?id=usb:046d-c545 https://linux-hardware.org/?id=usb:046d-c547 I do not have Solaar but using lsusb I can confirm i also have the C547.
Unsure if it can help, but here's the full output of lsusb -v -s 003:003 :
Bus 003 Device 003: ID 046d:c547 Logitech, Inc. USB Receiver
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 [unknown]
bDeviceSubClass 0 [unknown]
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x046d Logitech, Inc.
idProduct 0xc547 USB Receiver
bcdDevice 4.02
iManufacturer 1 Logitech
iProduct 2 USB Receiver
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0054
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 4 MPR04.02_B0009
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 98mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 83
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 1 Keyboard
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 133
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 [unknown]
bInterfaceProtocol 0
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 54
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Device Status: 0x0000
(Bus Powered)
Hey felix.fourcolor@gmail.com, Can you execute `lsusb -v -d 046d:C545` on you machine to see if there is any difference with C547. > Can you execute `lsusb -v -d 046d:C545` on you machine to see if there is any
> difference with C547.
Bus 001 Device 002: ID 046d:c545 Logitech, Inc. USB Receiver
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 [unknown]
bDeviceSubClass 0 [unknown]
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x046d Logitech, Inc.
idProduct 0xc545 USB Receiver
bcdDevice 2.01
iManufacturer 1 Logitech
iProduct 2 USB Receiver
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0054
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 4
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 98mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 83
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 1 Keyboard
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 133
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 [unknown]
bInterfaceProtocol 0
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 54
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Ok, so it makes sense that only 046d:c547 is affected as the change in https://github.com/torvalds/linux/commit/9d1bd9346241cd6963b58da7ffb7ed303285f684 creates new `#define USB_DEVICE_ID_LOGITECH_NANO_RECEIVER_LIGHTSPEED_1_2 0xc547` - but it seems that this same 0xc547 is used with G915 TKL as well, but does not have the 13 byte reports. Quick test reverting the report size did nothing.
Only thing that made my keyboard work again was to remove this code
[code]
{ /* Logitech lightspeed receiver (0xc547) */
HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH,
USB_DEVICE_ID_LOGITECH_NANO_RECEIVER_LIGHTSPEED_1_2),
.driver_data = recvr_type_gaming_hidpp},
[/code]
After that change, I am guessing the hidpp module is no longer loaded? I would assume you could also fix this by blacklisting hid_logitech_dj Correct, but I can't because I also have a logitech mouse (G603) that uses that module for properly functioning Blacklisting hid_logitech_dj is working for me. My keyboard and my mouse works as expected when this module is not loaded. The fallback module seems to work fine, but without the logitech hidppp module (blocked when hid_logitech_dj is blacklisted) some wireless functionality doesn't seem to work for me. Things like battery tracking for example. For the record, this problem also effects the G502 X family of computer mice. (In reply to Arthur Borsboom from comment #6) > Possibly related: Logitech G510s keyboard not working on kernel 6.6.1. > > [ 7.990759] sysfs: cannot create duplicate filename > '/devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:08.0/0000:07:00.0/ > 0000:08:0c.0/0000:0c:00.0/usb1/1-3/1-3:1.1/0003:046D:C22D.000B/leds/g15:: > kbd_backlight/color' We had a similar report on openSUSE Tumbleweed: https://bugzilla.suse.com/show_bug.cgi?id=1217172 This turned to be rather another issue. The culprit the commit in 6.6 c7d80059b086c4986cd994a1973ec7a5d75f8eea leds: class: Store the color index in struct led_classdev Now leds class creates "color" sysfs entry, and it conflicts with the already-existing "color" entry of hid-lg-g15 driver, which resulted in the probe error. A workaround patch is provided in the openSUSE Bugzilla entry above: https://bugzilla.suse.com/attachment.cgi?id=870817 Hi Takashi, The workaround patch should work, however a better solution has been discussed. Apparently the sysfs entry is not needed to be exported. An undo of this export should resolve the issue for all the keyboards using leds and other led drivers. This solution has been discussed here: https://lkml.org/lkml/2023/11/6/476 However, I haven't seen the actual patch yet. Maybe a friendly reminder would help? Also I believe the issue with the Logitech G510s keyboard has a different cause than the discussion in this bug report regarding the Logitech G915 keyboard. Thanks, good to hear that it's tracked in the upstream. And, yes, a ping might help. It's a severe breakage for many people who use those keyboard models and the fix itself should be trivial. Last but not least, it might be worth to open another bugzilla entry, too (if not present yet); otherwise it's confusing as if it were related problem with the original bug report. The Logitech G510s keyboard bug report: https://bugzilla.kernel.org/show_bug.cgi?id=218155 I have the Logitech G915TKL Keyboard and Logitech G502X mouse. I experienced the same issues when I updated to 6.6.1 today. The mouse, did not seem to stop working as expected, but the keyboard completely is all sorts of crazy on keys not working. Eaamme43 That was me typing: "This is me trying to type".. And I stopped because some key tried to reload the browser, F7 I presume. If any information is needed I'm more than willing to help out. I had the same issue on my logitech G502X mouse. The programmable buttons stopped working. After reverting commit 9d1bd9346241cd6963b58da7ffb7ed303285f684, functionality is restored. Props to loqs (https://bbs.archlinux.org/viewtopic.php?pid=2132894#p2132894) Fedora 39 just updated to kernel 6.6. Was greeted with this nice bug that completely wrecked G915 TKL:s lightspeed connection. The keys are completely scrambled. I am very disapppointed to see that this bug has been known for a while but completely ignored. I think this bug is severe as this is an input device bug for very expensive keyboard which is unacceptable. Please fix this bug ASAP. These kinds of things never ever happen on windows. I believe this is fixed in kernel 6.6.3 already. (In reply to Abdulla from comment #40) > I believe this is fixed in kernel 6.6.3 already. I can confirm that 6.6.3 (6.6.3-arch1-1 from Arch Linux, at least) resolves this issue. yes, they reverted it until original author come up with a proper fix. This bug report can be closed. as below: commit a302879747f8f5bf6ff578acf877f310e0cd3f2f Author: Jiri Kosina <jkosina@suse.cz> Date: Tue Nov 21 14:38:11 2023 +0100 Revert "HID: logitech-dj: Add support for a new lightspeed receiver iteration" commit 5b4ffb176d7979ac66b349addf3f7de433335e00 upstream. This reverts commit 9d1bd9346241cd6963b58da7ffb7ed303285f684. Multiple people reported misbehaving devices and reverting this commit fixes the problem for them. As soon as the original commit author starts reacting again, we can try to figure out why he hasn't seen the issues (mismatching report descriptors?), but for the time being, fix for 6.7 by reverting. Link: https://bugzilla.kernel.org/show_bug.cgi?id=218172 Link: https://bugzilla.kernel.org/show_bug.cgi?id=218094 Cc: <stable@vger.kernel.org> Signed-off-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> I can also confirm that this is fixed on 6.6.3 (6.6.3-2-cachyos here.), so i am marking this as resolved. Confirmed as well. Thank you all! |