Arch Linux

elliptic

Member

Registered: 2022-07-14

Posts: 4

Wine causes Logitech mouse input to break

Hi,

I've been banging my head with an issue I've had with Wine and my mouse for quite some time. Everytime I start an application under wine, whether it be "winecfg" or "wine foobar.exe", it seems to break my Logitech G Pro wireless mouse.

He's the output from wine (version: wine-8.13 (Staging)

007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
008c:err:ole:start_rpcss Failed to start RpcSs service
008c:err:ole:start_rpcss Failed to start RpcSs service
003c:err:service:process_send_command receiving command result timed out
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"winebus" failed to start: 1053
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.

Output from dmesg -w

[  525.294139] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[  525.299134] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[  525.303138] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[  525.306134] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[  525.309137] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[  525.311137] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[  525.313137] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[  525.314143] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[  525.315142] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[  525.316147] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[  525.317142] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[  525.318167] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[  525.319142] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[  525.320142] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[  525.321142] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[  525.322145] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[  525.323142] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[  525.324143] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[  525.325115] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[  525.326112] delayedwork_callback: delayedwork queued before hidpp interface was enumerated

Output from " lsmod | grep -i logitech"

hid_logitech_hidpp     77824  0
hid_logitech_dj        40960  0
usbhid                 77824  2 hid_logitech_dj,hid_logitech_hidpp

I believe it has something to do with the logitech module "hid_logitech_dj" but I could be wrong. Any help would be greatly appreciated and if you need more info please feel free to ask.

Last edited by elliptic (2023-07-30 01:41:38)

nbisby

Member

Registered: 2018-04-06

Posts: 5

Re: Wine causes Logitech mouse input to break

Trying to reboot didn't help.

I was also getting the delayedwork_callback spam anytime I moved the mouse while on the systemd shutdown screen. But also the "Sending SIGKILL to winedevice.exe" never ended. I waited quite a long time and my computer never actually rebooted. I just wound up hardware rebooting.
And for me, "wine" starts just from opening steam as it starts doing proton stuff in the background.

And to make things worse, I have a powerplay mousepad for wireless charging... And that wound up getting incredibly hot.

Using libratbag for logitech mouse support, and this is what i had show up in journalctl.

Jul 28 17:52:23 myself systemd[1]: Started Daemon to introspect and modify configurable mice.
Jul 28 18:05:12 myself ratbagd[35814]: ratbag error:     USB error: Input/output error (5)
Jul 28 18:05:12 myself ratbagd[35814]: write: Input/output error
Jul 28 18:05:12 myself ratbagd[35814]: ratbag error: Error: No such device (19)
Jul 28 18:05:12 myself ratbagd[35814]: ratbag error: Error: No such device (19)

Unplugged my powerplay mat and plugging the mouse in directly... and lsusb still thinks that the PowerPlay is still plugged in.

Seems like something is extremely wrong here. And it has me a bit nervous about safety, since the mousepad got to the point where I worry about it becoming a fire hazard.

Last edited by nbisby (2023-07-28 23:46:57)

nbisby

Member

Registered: 2018-04-06

Posts: 5

Re: Wine causes Logitech mouse input to break

Quick update:

based on a stack overflow article for a completely different problem, I wound up blacklisting the hid_logitech_dj kernel module... turns out this is what's causing the issue but also isn't used by the g pro wireless? My mouse is still working fine without it anyway. hid_logitech_hidpp seems to be handling everything
Launching steam still makes my mouse a bit jittery, but it doesn't completely stop moving (And that might just be the tons of games updating shaders in the background since I havent had steam open in a few weeks).

sudo rmmod hid_logitech_dj

and also put

blacklist hid_logitech_dj

into /etc/modprobe.d/blacklist.conf

elliptic

Member

Registered: 2022-07-14

Posts: 4

Re: Wine causes Logitech mouse input to break

I saw that solution as well but it comes at the cost of breaking libratbag and piper, so it feels more like a hackjob rather than a proper solution to the issue.

Last edited by elliptic (2023-07-30 01:44:47)

nbisby

Member

Registered: 2018-04-06

Posts: 5

Re: Wine causes Logitech mouse input to break

Agreed. It is definitely a hackjob, but makes for a tolerable workaround if you need wine urgently. The g pro wireless at least has onboard profiles, so you dont absolutely need piper and ratbag running constantly.

I'm not entirely sure which is at fault here though. Does this get resolved by reverting wine, or reverting the linux kernel?

elliptic

Member

Registered: 2022-07-14

Posts: 4

Re: Wine causes Logitech mouse input to break

I think it may be an arch kernel issue. I've reverted both my wine install (8.13 -> 8.0) and my linux kernel (6.4.7-arch1.1 -> 6.1.10-arch1.1) and the issues seems to have resolved. When I update my wine back to 8.13 on kernel 6.1.10 the issue also seems to have fixed itself.

However there is a moment where I still lose mouse control while launching winecfg but it comes back within a few seconds.

The logs when executing winecfg

007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.

elliptic

Member

Registered: 2022-07-14

Posts: 4

Re: Wine causes Logitech mouse input to break

I took a look at journalctl -xe today and appears that the kernel panics whenever I run winecfg

Aug 07 18:22:26 onion kernel: BUG: unable to handle page fault for address: ffffb327e3db19f8
Aug 07 18:22:26 onion kernel: #PF: supervisor write access in kernel mode
Aug 07 18:22:26 onion kernel: #PF: error_code(0x0002) - not-present page
Aug 07 18:22:26 onion kernel: PGD 100000067 P4D 100000067 PUD 1001e4067 PMD 0 
Aug 07 18:22:26 onion kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI
Aug 07 18:22:26 onion kernel: CPU: 10 PID: 2515 Comm: winedevice.exe Tainted: G          IOE      6.4.8-arch1-1 #1 32d>
Aug 07 18:22:26 onion kernel: Hardware name: ASUS System Product Name/PRIME Z390-A, BIOS 1903 07/08/2021
Aug 07 18:22:26 onion kernel: RIP: 0010:power_supply_uevent+0xee/0x1d0
Aug 07 18:22:26 onion kernel: Code: 75 4e 48 8b 13 48 83 7a 28 00 74 75 45 31 ff 31 c0 eb 10 48 8b 13 41 83 c7 01 49 6>
Aug 07 18:22:26 onion kernel: RSP: 0018:ffffb327c5e4f900 EFLAGS: 00010297
Aug 07 18:22:26 onion kernel: RAX: 0000000000000002 RBX: ffff89571750b000 RCX: ffff89577bb1b000
Aug 07 18:22:26 onion kernel: RDX: 00000000efb107ba RSI: 0000000000000000 RDI: ffff89571750b000
Aug 07 18:22:26 onion kernel: RBP: ffff89571750b038 R08: 0000000000000007 R09: ffff8958250922f5
Aug 07 18:22:26 onion kernel: R10: ffffffffffffffff R11: 0000000000000000 R12: ffff895725092000
Aug 07 18:22:26 onion kernel: R13: 0000000000000000 R14: ffff89577bb1b000 R15: 0000000000000002
Aug 07 18:22:26 onion kernel: FS:  00007ffffe5ff6c0(0000) GS:ffff89599dc80000(0000) knlGS:000000007ff70000
Aug 07 18:22:26 onion kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 07 18:22:26 onion kernel: CR2: ffffb327e3db19f8 CR3: 00000002de5f2001 CR4: 00000000003706e0
Aug 07 18:22:26 onion kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 07 18:22:26 onion kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Aug 07 18:22:26 onion kernel: Call Trace:
Aug 07 18:22:26 onion kernel:  <TASK>
Aug 07 18:22:26 onion kernel:  ? __die+0x23/0x70
Aug 07 18:22:26 onion kernel:  ? page_fault_oops+0x171/0x4e0
Aug 07 18:22:26 onion kernel:  ? exc_page_fault+0x175/0x180
Aug 07 18:22:26 onion kernel:  ? asm_exc_page_fault+0x26/0x30
Aug 07 18:22:26 onion kernel:  ? power_supply_uevent+0xee/0x1d0
Aug 07 18:22:26 onion kernel:  dev_uevent+0x10f/0x2d0
Aug 07 18:22:26 onion kernel:  kobject_uevent_env+0x291/0x680
Aug 07 18:22:26 onion kernel:  power_supply_unregister+0x8e/0xa0
Aug 07 18:22:26 onion kernel:  release_nodes+0x3d/0xb0
Aug 07 18:22:26 onion kernel:  devres_release_all+0x8c/0xc0
Aug 07 18:22:26 onion kernel:  device_unbind_cleanup+0xe/0x70
Aug 07 18:22:26 onion kernel:  device_unbind_cleanup+0xe/0x70
Aug 07 18:22:26 onion kernel:  device_unbind_cleanup+0xe/0x70
Aug 07 18:22:26 onion kernel:  device_release_driver_internal+0x1cc/0x200
Aug 07 18:22:26 onion kernel:  bus_remove_device+0xc6/0x130
Aug 07 18:22:26 onion kernel:  device_del+0x15c/0x3e0
Aug 07 18:22:26 onion kernel:  ? __queue_work+0x1df/0x440
Aug 07 18:22:26 onion kernel:  hid_destroy_device+0x4b/0x60
Aug 07 18:22:26 onion kernel:  logi_dj_remove+0x9a/0x100 [hid_logitech_dj db9e1e205ec4cdbc663ba1dffa7b1c9985ed100c]
Aug 07 18:22:26 onion kernel:  hid_device_remove+0x44/0x90
Aug 07 18:22:26 onion kernel:  device_release_driver_internal+0x19f/0x200
Aug 07 18:22:26 onion kernel:  bus_remove_device+0xc6/0x130
Aug 07 18:22:26 onion kernel:  device_del+0x15c/0x3e0
Aug 07 18:22:26 onion kernel:  ? __queue_work+0x1df/0x440
Aug 07 18:22:26 onion kernel:  hid_destroy_device+0x4b/0x60
Aug 07 18:22:26 onion kernel:  usbhid_disconnect+0x47/0x60 [usbhid 13f68ec49a4a3f9fbc196305e1c1a624b41d1554]
Aug 07 18:22:26 onion kernel:  usb_unbind_interface+0x90/0x270
Aug 07 18:22:26 onion kernel:  device_release_driver_internal+0x19f/0x200
Aug 07 18:22:26 onion kernel:  proc_ioctl+0x1be/0x230
Aug 07 18:22:26 onion kernel:  usbdev_ioctl+0x7f9/0x15a0
Aug 07 18:22:26 onion kernel:  ? current_time+0x40/0x110
Aug 07 18:22:26 onion kernel:  __x64_sys_ioctl+0x91/0xd0
Aug 07 18:22:26 onion kernel:  do_syscall_64+0x5d/0x90
Aug 07 18:22:26 onion kernel:  ? syscall_exit_to_user_mode+0x1b/0x40
Aug 07 18:22:26 onion kernel:  ? __x64_sys_ioctl+0xac/0xd0
Aug 07 18:22:26 onion kernel:  ? syscall_exit_to_user_mode+0x1b/0x40
Aug 07 18:22:26 onion kernel:  ? do_syscall_64+0x6c/0x90
Aug 07 18:22:26 onion kernel:  entry_SYSCALL_64_after_hwframe+0x72/0xdc
Aug 07 18:22:26 onion kernel: RIP: 0033:0x7f468730ce1f
Aug 07 18:22:26 onion kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 4>
Aug 07 18:22:26 onion kernel: RSP: 002b:00007ffffe5fe550 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Aug 07 18:22:26 onion kernel: RAX: ffffffffffffffda RBX: 00007f4674025690 RCX: 00007f468730ce1f
Aug 07 18:22:26 onion kernel: RDX: 00007ffffe5fe5b0 RSI: 00000000c0105512 RDI: 0000000000000028
Aug 07 18:22:26 onion kernel: RBP: 0000000000000028 R08: 00007ffffe5fe5f0 R09: 0000000000000000
Aug 07 18:22:26 onion kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 00007f4674025530
Aug 07 18:22:26 onion kernel: R13: 0000000000000000 R14: 00007f467403c8d0 R15: 00007f467402e9e0
Aug 07 18:22:26 onion kernel:  </TASK>
Aug 07 18:22:26 onion kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq rfcomm ccm cmac algif_hash algif_sk>
Aug 07 18:22:26 onion kernel:  snd_intel_dspcfg libarc4 btrtl uvcvideo kvm snd_intel_sdw_acpi snd_usbmidi_lib btbcm sn>
Aug 07 18:22:26 onion kernel:  spi_intel_pci cryptd xhci_pci spi_intel nvme_common xhci_pci_renesas nvidia_drm(OE) nvi>
Aug 07 18:22:26 onion kernel: CR2: ffffb327e3db19f8
Aug 07 18:22:26 onion kernel: ---[ end trace 0000000000000000 ]---
Aug 07 18:22:26 onion kernel: RIP: 0010:power_supply_uevent+0xee/0x1d0
Aug 07 18:22:26 onion kernel: Code: 75 4e 48 8b 13 48 83 7a 28 00 74 75 45 31 ff 31 c0 eb 10 48 8b 13 41 83 c7 01 49 6>
Aug 07 18:22:26 onion kernel: RSP: 0018:ffffb327c5e4f900 EFLAGS: 00010297
Aug 07 18:22:26 onion kernel: RAX: 0000000000000002 RBX: ffff89571750b000 RCX: ffff89577bb1b000
Aug 07 18:22:26 onion kernel: RDX: 00000000efb107ba RSI: 0000000000000000 RDI: ffff89571750b000
Aug 07 18:22:26 onion kernel: RBP: ffff89571750b038 R08: 0000000000000007 R09: ffff8958250922f5
Aug 07 18:22:26 onion kernel: R10: ffffffffffffffff R11: 0000000000000000 R12: ffff895725092000
Aug 07 18:22:26 onion kernel: R13: 0000000000000000 R14: ffff89577bb1b000 R15: 0000000000000002
Aug 07 18:22:26 onion kernel: FS:  00007ffffe5ff6c0(0000) GS:ffff89599dc80000(0000) knlGS:000000007ff70000
Aug 07 18:22:26 onion kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 07 18:22:26 onion kernel: CR2: ffffb327e3db19f8 CR3: 00000002de5f2001 CR4: 00000000003706e0
Aug 07 18:22:26 onion kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 07 18:22:26 onion kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Aug 07 18:22:26 onion kernel: note: winedevice.exe[2515] exited with irqs disabled
Aug 07 18:22:26 onion org_kde_powerdevil[1598]: QObject::disconnect: Unexpected nullptr parameter
Aug 07 18:22:26 onion org_kde_powerdevil[1598]: QObject::disconnect: Unexpected nullptr parameter

hopefully that can provide some information to somebody who is more experienced with this than I am.

Broccoleader

Member

Registered: 2023-08-28

Posts: 1

Re: Wine causes Logitech mouse input to break

I'm on Endeavour OS and I can confirm the very same behaviour.

When I opened a program through Wine, Solaar would just completely crap itself and my Logitech mouse would not connect anymore. Even plugging in a different mouse at that point wouldn't work.
The shutdown would then languish on and on and would require a hardware reboot like you mentioned.

I uninstalled Solaar and at least now there's only a momentary mouse input break when launching a program through Wine (like you described in the OP).

Subscribed to the topic to stay up to date.

padajuan

Member

Registered: 2023-09-23

Posts: 1

Re: Wine causes Logitech mouse input to break

exactly the same issues here on EndeavourOS aswell

nbisby

Member

Registered: 2018-04-06

Posts: 5

Re: Wine causes Logitech mouse input to break

Installed linux 6.6 from core-testing, and turned hid_logitech_dj back on and having no problems so far. Piper working and wine games working.