Ubuntu 22.04.1: How to automatically reset USB connections upon wake?

I have a Lenovo ThinkPad E15 that came with Windows 10 installed. I added Ubuntu 22.04.1 as an option (dual-boot).

Whenever the laptop sleeps (goes into a "suspend" state) and then later I wake it up, the Logitech wireless mouse scroll wheel doesn't work. ("Logitech MK270 Wireless Keyboard and Mouse Combo", but the only thing that doesn't work is the scroll wheel.)

I already asked about this problem, and I gave a bounty for an answer that helped me make progress but didn't fully solve it.

Currently the result of cat /etc/systemd/system/reset-usb-upon-wake@.service is:

[Unit]
Description="Reset a USB device after system resume"
After=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target

[Service]
Type=simple
ExecStart=/usr/bin/usbreset %i
User=root
Group=root

[Install]
WantedBy=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target

When I wake the computer, the mouse scroll wheel doesn't work.

I run sudo systemctl status reset-usb-upon-wake@046d:c534.service and see:

○ reset-usb-upon-wake@046d:c534.service - "Reset a USB device after system resume"
     Loaded: loaded (/etc/systemd/system/reset-usb-upon-wake@.service; disabled; vendor preset: enabled)
     Active: inactive (dead)

Then I run sudo systemctl start reset-usb-upon-wake@046d:c534.service, and the result is:

• It prints a bunch of empty newlines to the terminal infinitely until I cancel out of the command. ‍♀️
• After exiting that command, my scroll wheel works again.
• sudo systemctl status reset-usb-upon-wake@046d:c534.service still shows "inactive (dead)".

I also tried sudo systemctl enable reset-usb-upon-wake@046d:c534.service, but the status still shows as dead after running that too.

How can I completely fix this problem so that I never have to think about my scroll wheel and it always works, even after waking from sleep?

P.S. I also tried sudo vim /etc/udev/rules.d/99-usbreset.rules and saving these lines to that new file:

# Reset Logitech wireless mouse on resume from sleep
SUBSYSTEM=="usb", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c534", RUN+="/usr/bin/usbreset %p"

P.P.S. In response to an answer:

lsusb && lsmod | grep usbhid
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 008: ID 27c6:55a4 Shenzhen Goodix Technology Co.,Ltd. Goodix FingerPrint Device
Bus 003 Device 006: ID 30c9:0014 Luxvisions Innotech Limited Integrated Camera
Bus 003 Device 039: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 003 Device 038: ID 046d:0825 Logitech, Inc. Webcam C270
Bus 003 Device 040: ID 0d8c:0014 C-Media Electronics, Inc. Audio Adapter (Unitek Y-247A)
Bus 003 Device 037: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 003 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 003 Device 004: ID 0451:82ff Texas Instruments, Inc. 
Bus 003 Device 002: ID 0451:8442 Texas Instruments, Inc. 
Bus 003 Device 009: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
usbhid                 65536  1 hid_logitech_dj
hid                   151552  7 i2c_hid,hid_cmedia,usbhid,hid_multitouch,hid_generic,hid_logitech_dj,hid_logitech_hidpp

UPDATE 2:

lsmod | grep hid_logitech_dj && lsmod | grep hid_logitech_hidpp
hid_logitech_dj        28672  0
usbhid                 65536  1 hid_logitech_dj
hid                   151552  7 i2c_hid,hid_cmedia,usbhid,hid_multitouch,hid_generic,hid_logitech_dj,hid_logitech_hidpp
hid_logitech_hidpp     49152  0
hid                   151552  7 i2c_hid,hid_cmedia,usbhid,hid_multitouch,hid_generic,hid_logitech_dj,hid_logitech_hidpp

How to detect reset-able USB devices?

Just run usbreset and it should tell you what it can do and how ... e.g. like so:

$ usbreset 
Usage: # <=== This is how to do it (reset devices)
  usbreset PPPP:VVVV - reset by product and vendor id
  usbreset BBB/DDD   - reset by bus and device number
  usbreset "Product" - reset by product name

Devices: # <=== These are the devices that it sees and can reset
  Number 001/002  ID 8087:0a3a  
  Number 001/005  ID 05ac:14a7  iPhone
  Number 001/003  ID 0bda:55ea  EasyCamera

So, how to auto execute upon system wake up from sleep?

A simple and yet very reliable way is to create a script in /lib/systemd/system-sleep/ that reads the positional parameter $1 and runs commands accordingly.

Executable files in that directory will be run before and after system sleep/suspend, hibernate, or hybrid-sleep with two positional parameters passed to them ... $1 will hold either pre or post and $2 will hold the action i.e. sleep, hibernate ... etc.

The procedure will be like so:

• Create the script file and open it for editing ... e.g. like so:

  sudo nano /lib/systemd/system-sleep/fix-my-mouse-wheel
  

• Use this template in the file ... i.e. copy/paste it in the file then modify it to add your command(s) in the right section then save the file afterwords:

  #!/bin/sh
  
  case "${1}" in
    pre)
      # Command(s)/script(s) "each on a newline" to be executed before system goes to sleep/hibernate
        ;;
    post)
      sleep 5 # You most likely will need this sleep call. Leave it alone.
      # Command(s)/script(s) "each on a newline" to be executed after system wakes up from sleep/hibernate
      # e.g. usbreset 05ac:14a7
        ;;
  esac
  

• Make it executable like so:

  sudo chmod +x /lib/systemd/system-sleep/fix-my-mouse-wheel
  

• Done.

I had this same problem for a while(in recent ubuntu installs), and no scripts that I saw suggested anywhere as a solution worked for me.

In the end modprobe did the trick, but here is the catch:

If you lsmod | grep usbhid

You might see that usbhid is "used by"(second column) something else. In my case, I draw often, and so I see a 'wacom' listed there. This means that after a suspend I have to do(the order matters):

sudo rmmod wacom && sudo rmmod usbhid && sudo modprobe usbhid && sudo modprobe wacom

If I rmmod usbhid before 'wacom' it errors out and the process does nothing because of the dependency issue. If it's a clean startup i can just do the rmmod/modprobe combo on usbhid and it works.

Now, my device is a Msoft keyboard/mouse combo and it uses the usbhid only, the logitech device might be different, I saw in the other post that you claimed it uses hid_logitech_dj also, but you also said that modprobing it doesnt work. The question is where did you get that name from, did you find it with lsmod as depicted above? I don't see why modprobing wouldn't work if you figure out what you actually have to unload/reload, in your specific system.

Instead of chaining commands, try doing one command at a time and see if any of them return errors.

Your case might be a specific edge case so who knows. It's a shame that Canonical hasn't looked into this, it's like some old suspension bug that took years to be fixed.

I hope this helps you, even if you hit another dead end, don't give up. As depicted above, in principle, this problem is not unsolvable.

Edit:

This issue seems connected with new Linux Kernel 5 features that implemented fancy mouse support.

In the case of some Logitech and other mouses it's possible that simply cycling the modules doesn't work because of the mouse wheel high precision/sensitivity. As per the Solaar post, users would have to reset the mouse wheel to get it to function, otherwise it would be active but seems inactive or slow.

Useful Links:

1.Another post with similar solutions.

2.Launchpad Post with similar problem

3.Logitech firmware bug report

4.Solaar issue (Solaar is a Linux device manager for Logitech devices)

5.Linux kernel bug report

[Unit]                                                                                                                                                       
Description="Reset a USB device after system resume"                                                                                                         
After=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target                                                                      
                                                                                                                                                             
[Service]                                                                                                                                                    
Type=simple                                                                                                                                                  
ExecStart=/usr/bin/usbreset 046d:c534                                                                                                                  
User=root                                                                                                                                                    
Group=input                                                                                                                                                  
[Install]                                                                                                                                                    
WantedBy=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target                                 

I think udev will not work in this case.

sudo systemctl enable reset-usb-upon-wake@046d:c534.service

Then let systemd know something changed.

sudo systemctl daemon-reload