[Solved] Mouse often needs to be replugged when booting desktop

[MiracleDinner]

Hello,

I've been experiencing an issue on my desktop PC for a while now, which is that around half the time (it seems random) when I boot my PC, the mouse doesn't respond unless I unplug and replug my mouse from the USB port. This is very inconvenient to have to do, as my PC is under the desk, and the mouse is plugged into the back.

My mouse is the Logitech G305 wireless mouse.

Thanks very much in advance for any advice.

[Ardouos]

Can you move the mouse around or does nothing happen at all?

What does dmesg say?

[pbear]

Shot in the dark. Maybe the battery needs to be replaced?

[FreewheelinFrank]

Assuming its not the battery, can you run

Code: Select all

$ usbreset

Output should show your mouse:

Code: Select all

Usage:
  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:

  Number 001/007  ID 17ef:602e  USB Optical Mouse

Next time the mouse isn't responding, run

Code: Select all

# usbreset "USB Optical Mouse"

Edit: change for the actual name of your device, obviously.

(or use product/vendor or bus/device ID).

If that works, it is possible to autorun the command after suspend. See:

https://askubuntu.com/questions/1044988 ... untu-18-04

[Aki]

Hello,

My mouse is the Logitech G305 wireless mouse.

It looks like a wireless mouse [1] and has its own USB receiver.

So you're not unplugging the mouse, you're unplugging the USB receiver, right?

You can therefore rule out other causes (environmental interference ? distance from the receiver (> 20 cm) ? low battery in the mouse ? ).

--
[1] G305 LIGHTSPEED Wireless Gaming Mouse SETUP GUIDE

[MiracleDinner]

Yes, it is the USB receiver that I need to unplug and replug.

I doubt it is "environmental interference" of any sort - the mouse is just on top of the wooden desk, and the desktop is under it.

The distance could be a factor, as it's indeed >20cm - perhaps I could test temporarily placing my mouse nearby to see if that affects anything. But the position of the mouse doesn't change when I unplug and replug the receiver, which always fixes the problem until the next reboot.

Here is the output of upower -i, what does this mean as it says "should be ignored" next to the line saying the percentage is 100%?

Code: Select all

miracledinner@miracledinner-b550aoruselitev2:~$ upower -i /org/freedesktop/UPower/devices/battery_hidpp_battery_0
  native-path:          hidpp_battery_0
  model:                G305 Lightspeed Wireless Gaming Mouse
  serial:               8d-df-b8-65
  power supply:         no
  updated:              Sun 14 Apr 2024 20:10:52 BST (6 seconds ago)
  has history:          yes
  has statistics:       yes
  mouse
    present:             yes
    rechargeable:        yes
    state:               fully-charged
    warning-level:       none
    battery-level:       full
    percentage:          100% (should be ignored)
    icon-name:          'battery-full-charged-symbolic'
  History (charge):
    1713121762	100.000	fully-charged
    1713121762	0.000	unknown
  History (rate):
    1713121762	0.000	unknown

Note also that my mouse is powered by a single AA battery.

[Aki]

Hello @MiracleDinner,
Did you sorted it out ?

[MiracleDinner]

Hi,

Apologies for not updating about this sooner.

It does seem as if placing my mouse on top of the desktop whilst it is booting - and thus shortening the distance between the mouse and receiver - fixes the problem most or all of the time. I think I have had a couple of incidents where I still had to replug it, but I don't know maybe the mouse wasn't quite close enough or maybe it could use a new battery.

It's a little inconvenient to have to do every time but much less so than having to unplug and replug the receiver.

Also apologies that I didn't see, and therefore didn't reply to the messages prior to Aki's. The problem did involve being unable to move the mouse whatsoever. If it happens again, I will try running dmesg and usbreset.

[pbear]

... maybe it could use a new battery.

Frankly, pretty silly you haven't replaced it already. Not expensive, maybe solves the problem.

[Aki]

Hello,

It does seem as if placing my mouse on top of the desktop whilst it is booting - and thus shortening the distance between the mouse and receiver - fixes the problem most or all of the time. I think I have had a couple of incidents where I still had to replug it, but I don't know maybe the mouse wasn't quite close enough or maybe it could use a new battery.

It's a little inconvenient to have to do every time but much less so than having to unplug and replug the receiver.

Also apologies that I didn't see, and therefore didn't reply to the messages prior to Aki's. The problem did involve being unable to move the mouse whatsoever. If it happens again, I will try running dmesg and usbreset.

Don't worry, the important thing is that you've sorted it out.

When you believe it is reasonably fixed, please, mark the discussion as "solved" manually adding the text tag "[Solved]" at the beginning of the subject of the first message.

Happy Debian !

[MiracleDinner]

So I just experienced this problem once again, but this time there was an identifiable possible cause: the mouse had been left switched on for over 24 hours beforehand. I did try running dmesg and usbreset but they didn't seem to fix it.

[MiracleDinner]

I have replaced the battery but I still experience this issue occasionally, even after placing the mouse near to the receiver and not having left it switched on beforehand, and usbreset didn't work either. Here is the dmesg output after unplugging and replugging the receiver.

https://pastebin.com/9ZVDMYyT