USB mouse pointer doesn't work on resume from suspend

Support
, , ,
1

On each resume from suspend USB mouse pointer doesn’t work whereas mouse left/right button + scroll wheel work, keyboard, touchpad do work, and usb-mouse light-indicators are blinking.
The related old story: USB mouse not working on resume from suspend - Technical Issues and Assistance - Manjaro Linux Forum
The proposed services don’t work (in my context).
I also tried to manually rebind the mouse by:
echo 0 > /sys/bus/usb/devices/... (waited 1 sec) than echo 1 > /sys/bus/usb/devices/... - but no effect.

Details:

$ inxi
CPU: 6-Core Intel Core i7-8750H (-MT MCP-) speed/min/max: 800/800/4100 MHz Kernel: 5.10.59-1-MANJARO x86_64
Up: 49m Mem: 5609.8/15864.9 MiB (35.4%) Storage: 2.05 TiB (15.3% used) Procs: 344 Shell: Bash inxi: 3.3.06

$ inxi -J
USB:       Hub-1: 1-0:1 info: Full speed (or root) Hub ports: 16 rev: 2.0
           Device-1: 1-2:2 info: ASUSTek ASUS ROG GAMING MOUSE GX900 type: Mouse,Keyboard rev: 2.0
           Device-2: 1-5:3 info: Realtek Integrated Webcam type: Video rev: 2.0
           Device-3: 1-6:4 info: Realtek RTS5129 Card Reader Controller type: <vendor specific> rev: 2.0
           Device-4: 1-14:5 info: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: Bluetooth rev: 2.0
           Hub-2: 2-0:1 info: Full speed (or root) Hub ports: 8 rev: 3.1

Any thoughts?

2
Just draft/pure thoughts

Is it mouse pointer freezing issue like mouse movement sensor stop to respond completely and pointer stucks in some position on display?

Does mouse pointer is visible or it is invisible/absent on the screen?

Check Manjaro power/suspend policies for devices and USB ports (that user found some USB suspend settings (for his case): Troubleshooting USB 3.0 Ethernet adapter).

Check your BIOS/UEFI settings for suspend/resume USB port. Try modes to suspend all, to never suspend. to turn on/off USB 2.0 mode (probably compatibility/legacy mode).

Does that device(s) has updatable firmware? Have lastest version already? May be to try downgrade it to -1, -2 version back and to check?

Does that effect present with every kernel version? May be to try at least couple of LTS (and may be now fixed) and 5.13, 5.14 versions?

How are you bring mouse pointer to live? By re-plug it? By turning wireless mouse off and on by switch on it?
If to re-plug that USB mouse (ot it’s wireless USB receiver), than mouse pointer become movable on screen again?

What manufacturer thinks? Did you open a tech. support ticket at least with the reason of what to try check?

Do you have other hardware?
Does other mouse HW behaves the same way on the PC?
Does other PC HW with the trouble mouse HW behaves the same way?

If the mouse is wireless, do you have re-chargeable battery? If to switch to new non-chargeable energy item, than does this happen again? (may be it need high current on start stage (for example like HDDs need to spin up their disks) and old re-chargeable battery can’t meet that requirements)

It is gaming mouse? Probably you have a HW key on the mouse to switch it’s sensitivity (or key combination - check user manual). May be switching the sensitivity mode (dpi/ppi) will trigger sensor mode and leads to wake it up or just some modes are fails to resume and other works fine.

re-read user manual fully, may be you will get another idea to try. Also read updatable trouble shooting and FAQ sections on it’s website.

if it is wireless mouse, it is possible to change USB receiver to other sample of the same model or other model (and to re-pair receiver w/ mouse)?

try another USB port (2.0/3.0) other side, back side.

visit service center of mouses/keyboards repair(fix): what are their advises?

if wireless did you tried to pair usb receiver and mouse again?

remove any additional adapters between mouse USB receiver (or mouse USB plug) and USB port of PC, so plugin the mouse directly into USB port of PC.

Is it possible to pass additional parameters into suspending mode to make PC to do not suspend USB ports or to suspend, turn off them fully (not some partial mode e.g. half-suspend)?

1 Like
3
  • It’s not visible on resume.
  • I don’t see such policies for USB mouses, unfortunately.
  • I carry that issue since 5.4 (for over 2 years)
  • Yes, replugging it. It looks “amazing” from outside. )
    But … When the suspend time (from closing my laptop lid) is quite short: say, from seconds to few minutes - the mouse pointer looks alive and stays movable on resume.

I might accept that the mouse is old and unsupported and it’s not Manjaro imperfectness.
But the mouse a handy and workable mouse and the issue is quite strange in general.
Thanks.

4

There are some idea tries remains unclear for me:

Want to try it or “I do not know there it is.” is more suitable in your case? Why not to try to ask that user?
@Dor, give us a hint how did you

please.

By providing a links to Ukranian/Russian websites, you could cut English speaking auditory.
And better to provide a link to manufacturer site, not to a shop.
I found the device here: https://www.asus.com/supportonly/gx900/HelpDesk_Download/
and manuals, including specs here:
https://dlcdnets.asus.com/pub/ASUS/Accessory/Mouse/GX900/E5887_ASUS_GX900_Gaming_Mouse.pdf
and
https://dlcdnets.asus.com/pub/ASUS/Accessory/Mouse/GX900/Q6264_GX900.zip (with PDF inside)

You can try to switch to a Windows PC, to install driver, and in that utility GUI to try to find that “update firmware” item.
Moreover, try to reset every thing to default and to save

image
image864×885 50.3 KB

this could re-initialize some functions/functionality of device including suspend mode.

But may be to try latest 5.14 could be a possible solution. I doubt also, but if you ran out of ideas, why not to try that also?

The https://www.asus.com/supportonly/GX900/HelpDesk_download/ says:

image
image693×763 54.8 KB

?

image
image723×979 116 KB

Also, if to read and to understood both summary pdf and user manual, that could brings you new ideas to try.

or to call them

?

?

So, one of possible ways of fixing it to install that for Arch-family OS (which already works on Ubuntu) to learn how it could be?

Try to figure out which delay leads to unrecoverable suspend and which is not. the timeout value could hint to someone the source of problem.

Try to find all logging sources on Manjaro. Main probably journalctl.
After that, wait for unrecoverable delay on mouse, write down exact time with seconds when you wake it up the device and try to find suspend event (event mode, event parameters) at the time of suspend and see what logs says about what is going in the system, while you try to resume.

Hm, like device is not recognized as device having pointer. Some sub-system do not wake up.

5

@RomanPerekhrest, how is it going?

Did I hurt you with my long posts? Sorry. That was not the purpose: posted raw ideas to proccess by you: to systematize, arrange, assume, select some and to try.

Check that thread also: Bluetooth: disable energy saving?
It is about:

Where can I disable energy saving/suspend [for USB ports]?

6

@alven

There’s no specific suspend/power-saving option for USB post/mouse in my BIOS.

I don’t have other mouse, unfortunately.

Tried: has the same effect.

There’s no such. Got a single USB post on the right side of my laptop, used right for the mouse.

That’s interesting observation: when I close the lid and open it after 30 sec - the mouse pointer is alive, when it takes to 60 sec - it becomes inactive.
Everytime I replug the mouse dmesg emits the following:

[28540.140247] usb 1-2: USB disconnect, device number 9
[28546.003170] usb 1-2: new full-speed USB device number 10 using xhci_hcd
[28546.161862] usb 1-2: New USB device found, idVendor=0b05, idProduct=1795, bcdDevice= 7.10
[28546.161864] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[28546.161865] usb 1-2: Product: ASUS ROG GAMING MOUSE GX900
[28546.161866] usb 1-2: Manufacturer: ASUS Compuer Inc.
[28546.164824] input: ASUS Compuer Inc. ASUS ROG GAMING MOUSE GX900 as /devices/pci0000:00/0000:00:14.0/u
sb1/1-2/1-2:1.0/0003:0B05:1795.000C/input/input58
[28546.165021] hid-generic 0003:0B05:1795.000C: input,hidraw0: USB HID v1.11 Mouse [ASUS Compuer Inc. ASU
S ROG GAMING MOUSE GX900] on usb-0000:00:14.0-2/input0
[28546.166138] input: ASUS Compuer Inc. ASUS ROG GAMING MOUSE GX900 Keyboard as /devices/pci0000:00/0000:
00:14.0/usb1/1-2/1-2:1.1/0003:0B05:1795.000D/input/input59
[28546.220230] input: ASUS Compuer Inc. ASUS ROG GAMING MOUSE GX900 Consumer Control as /devices/pci0000:
00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:0B05:1795.000D/input/input60
[28546.220471] hid-generic 0003:0B05:1795.000D: input,hidraw1: USB HID v1.11 Keyboard [ASUS Compuer Inc.
ASUS ROG GAMING MOUSE GX900] on usb-0000:00:14.0-2/input1
1 Like
7

Re-plug event log is not informative (as I can judge it): it saying that new device detected only (but yet can show it’s work mode).

here is mine plug in log if you want to compare 
Sep 29 01:06:49 pc kernel: usb 1-5: USB disconnect, device number 4
Sep 29 01:07:01 pc kernel: usb 1-5: new full-speed USB device number 7 using xhci_hcd
Sep 29 01:07:01 pc kernel: usb 1-5: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=12.07
Sep 29 01:07:01 pc kernel: usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Sep 29 01:07:01 pc kernel: usb 1-5: Product: USB Receiver
Sep 29 01:07:01 pc kernel: usb 1-5: Manufacturer: Logitech
Sep 29 01:07:01 pc kernel: logitech-djreceiver 0003:046D:C52B.0009: hiddev96,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-5/input2
Sep 29 01:07:01 pc kernel: input: Logitech K360 as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.2/0003:046D:C52B.0009/0003:046D:4004.000A/input/input21
Sep 29 01:07:01 pc kernel: logitech-hidpp-device 0003:046D:4004.000A: input,hidraw2: USB HID v1.11 Keyboard [Logitech K360] on usb-0000:00:14.0-5/input2:1
Sep 29 01:07:01 pc kernel: input: Logitech Wireless Device PID:4055 as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.2/0003:046D:C52B.0009/0003:046D:4055.000B/input/input22
Sep 29 01:07:01 pc kernel: logitech-hidpp-device 0003:046D:4055.000B: input,hidraw3: USB HID v1.11 Mouse [Logitech Wireless Device PID:4055] on usb-0000:00:14.0-5/input2:2
Sep 29 01:07:05 pc kernel: logitech-hidpp-device 0003:046D:4055.000B: HID++ 4.5 device connected.
Sep 29 01:07:09 pc kernel: logitech-hidpp-device 0003:046D:4004.000A: HID++ 2.0 device connected.

It is wireless USB receiver plugged out and in with 2 devices paired to it: keyboard and mice.
The current kernel is:

$ mhwd-kernel -li
Currently running: 5.15.0-1-MANJARO (linux515)
The following kernels are installed in your system:
   * linux515
$ pacman -Qi linux515 | grep Version
Version         : 5.15.rc3.210926.g5816b3e-1
$

May be log messages of the suspend action itself is more valuable?
What if to:

  • write down local system time of the PC to a paper
  • make that 60 secs delay,
  • write down system time again as end of suspending
  • view what happened during that 60 seconds

?

And after delay better to make

$ sync

first: it let to dump all info which could still be in cached in RAM into journals (to synchronize cached writes to persistent storage)
and than

$ journalctl -k

or even to view all events during that time interval

$ journalctl -b

may be you will find something there? at least to find the source (app name / kernel module name) which reports that mouse has been suspended. And after that to dig into learning that app/kernel module in try to setup it to fix that behavior? Also there is a small chance that UEFI/BIOS fimware or USB mouse firmware update will fix that (case of USB Controller needs to be replugged in to work - #18 by thecrimsoneye But that user “prefer to hide” (not noted) the info which firmware update fixed that issue of: UEFI or USB device).

8

Thanks for that advice.
Here are journal messages logged within the needed/measured time window:

$ journalctl --since "2021-10-04 15:26:02" --until "2021-10-04 15:27:10"
-- Journal begins at Mon 2020-12-28 17:39:13 EET, ends at Mon 2021-10-04 17:07:21 EEST. --
жов 04 15:26:02 roman-pc systemd-logind[1669]: Lid closed.
жов 04 15:26:03 roman-pc ModemManager[1716]: <info>  [sleep-monitor] system is about to suspend
жов 04 15:26:03 roman-pc kded5[1924]: bluedevil: About to suspend
жов 04 15:26:03 roman-pc NetworkManager[1666]: <info>  [1633350363.0052] manager: sleep: sleep requested (sleeping: no  enabled: yes)
жов 04 15:26:03 roman-pc NetworkManager[1666]: <info>  [1633350363.0054] device (wlo1): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
жов 04 15:26:03 roman-pc NetworkManager[1666]: <info>  [1633350363.0057] device (wlo1): set-hw-addr: reset MAC address to B4:69:21:52:16:D8 (unmanage)
жов 04 15:26:03 roman-pc NetworkManager[1666]: <info>  [1633350363.0061] device (p2p-dev-wlo1): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
жов 04 15:26:03 roman-pc NetworkManager[1666]: <info>  [1633350363.0063] manager: NetworkManager state is now ASLEEP
жов 04 15:26:03 roman-pc NetworkManager[1666]: <info>  [1633350363.0064] device (enp59s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
жов 04 15:26:03 roman-pc kded5[1924]: plasma-nm: Unhandled active connection state change:  3
жов 04 15:26:03 roman-pc dbus-daemon[1665]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=1666 comm="/usr/bin/NetworkManager --no-daemon ")
жов 04 15:26:03 roman-pc systemd[1]: Starting Network Manager Script Dispatcher Service...
жов 04 15:26:03 roman-pc dbus-daemon[1665]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
жов 04 15:26:03 roman-pc systemd[1]: Started Network Manager Script Dispatcher Service.
жов 04 15:26:03 roman-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
жов 04 15:26:03 roman-pc kernel: audit: type=1130 audit(1633350363.042:625): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
жов 04 15:26:03 roman-pc NetworkManager[1666]: <info>  [1633350363.0933] device (enp59s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
жов 04 15:26:03 roman-pc avahi-daemon[1662]: Withdrawing address record for fe80::3e2c:30ff:fe99:9d6 on enp59s0.
жов 04 15:26:03 roman-pc avahi-daemon[1662]: Leaving mDNS multicast group on interface enp59s0.IPv6 with address fe80::3e2c:30ff:fe99:9d6.
жов 04 15:26:03 roman-pc NetworkManager[1666]: <info>  [1633350363.0951] dhcp4 (enp59s0): canceled DHCP transaction
жов 04 15:26:03 roman-pc avahi-daemon[1662]: Interface enp59s0.IPv6 no longer relevant for mDNS.
жов 04 15:26:03 roman-pc NetworkManager[1666]: <info>  [1633350363.0951] dhcp4 (enp59s0): state changed bound -> terminated
жов 04 15:26:03 roman-pc kernel: r8169 0000:3b:00.0 enp59s0: Link is Down
жов 04 15:26:03 roman-pc avahi-daemon[1662]: Withdrawing address record for 176.36.3.30 on enp59s0.
жов 04 15:26:03 roman-pc avahi-daemon[1662]: Leaving mDNS multicast group on interface enp59s0.IPv4 with address 176.36.3.30.
жов 04 15:26:03 roman-pc skypeforlinux.desktop[2177]: ioctl failed for wlan0, errno = 19 (No such device)
жов 04 15:26:03 roman-pc skypeforlinux.desktop[2177]: ioctl failed for wlp2s0, errno = 19 (No such device)
жов 04 15:26:03 roman-pc skypeforlinux.desktop[2177]: ioctl failed for wlp3s0, errno = 19 (No such device)
жов 04 15:26:03 roman-pc skypeforlinux.desktop[2177]: ioctl failed for wlp4s0, errno = 19 (No such device)
жов 04 15:26:03 roman-pc avahi-daemon[1662]: Interface enp59s0.IPv4 no longer relevant for mDNS.
жов 04 15:26:03 roman-pc systemd-resolved[1653]: enp59s0: Bus client reset search domain list.
жов 04 15:26:03 roman-pc systemd-resolved[1653]: enp59s0: Bus client set default route setting: no
жов 04 15:26:03 roman-pc systemd-resolved[1653]: enp59s0: Bus client reset DNS server list.
жов 04 15:26:03 roman-pc NetworkManager[1666]: <warn>  [1633350363.1141] device (enp59s0): queue-state[unmanaged, reason:sleeping, id:86937]: replace previously queued state change
жов 04 15:26:03 roman-pc NetworkManager[1666]: <info>  [1633350363.1154] device (enp59s0): state change: disconnected -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
жов 04 15:26:03 roman-pc kded5[1924]: plasma-nm: Not emitting connection deactivated notification as we're about to suspend
жов 04 15:26:03 roman-pc kded5[1924]: plasma-nm: Network connectivity limited, scheduling notification
жов 04 15:26:04 roman-pc systemd-resolved[1653]: Switching to fallback DNS server 1.1.1.1.
жов 04 15:26:06 roman-pc NetworkManager[1666]: <info>  [1633350366.1329] device (enp59s0): carrier: link connected
жов 04 15:26:06 roman-pc NetworkManager[1666]: <info>  [1633350366.1331] device (enp59s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
жов 04 15:26:06 roman-pc kernel: r8169 0000:3b:00.0 enp59s0: Link is Up - 1Gbps/Full - flow control off
жов 04 15:26:08 roman-pc systemd-logind[1669]: Delay lock is active (UID 0/root, PID 1666/NetworkManager) but inhibitor timeout is reached.
жов 04 15:26:08 roman-pc systemd[1]: Created slice User Slice of UID roman.
жов 04 15:26:08 roman-pc systemd[1]: Reached target Sleep.
жов 04 15:26:08 roman-pc systemd[1]: Starting System Suspend...
жов 04 15:26:08 roman-pc systemd-sleep[141363]: Entering sleep state 'suspend'...
жов 04 15:26:08 roman-pc kernel: PM: suspend entry (deep)
жов 04 15:26:08 roman-pc kernel: Filesystems sync: 0.263 seconds
жов 04 15:27:04 roman-pc kernel: Freezing user space processes ... (elapsed 0.004 seconds) done.
жов 04 15:27:04 roman-pc kernel: OOM killer disabled.
жов 04 15:27:04 roman-pc kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
жов 04 15:27:04 roman-pc kernel: printk: Suspending console(s) (use no_console_suspend to debug)
жов 04 15:27:04 roman-pc kernel: r8169 0000:3b:00.0 enp59s0: Link is Down
жов 04 15:27:04 roman-pc kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
жов 04 15:27:04 roman-pc kernel: sd 1:0:0:0: [sdb] Stopping disk
жов 04 15:27:04 roman-pc kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
жов 04 15:27:04 roman-pc kernel: sd 0:0:0:0: [sda] Stopping disk
жов 04 15:27:04 roman-pc kernel: ACPI: EC: interrupt blocked
жов 04 15:27:04 roman-pc kernel: ACPI: Preparing to enter system sleep state S3
жов 04 15:27:04 roman-pc kernel: ACPI: EC: event blocked
жов 04 15:27:04 roman-pc kernel: ACPI: EC: EC stopped
жов 04 15:27:04 roman-pc kernel: PM: Saving platform NVS memory
жов 04 15:27:04 roman-pc kernel: Disabling non-boot CPUs ...
жов 04 15:27:04 roman-pc kernel: smpboot: CPU 1 is now offline
жов 04 15:27:04 roman-pc kernel: smpboot: CPU 2 is now offline
жов 04 15:27:04 roman-pc kernel: smpboot: CPU 3 is now offline
жов 04 15:27:04 roman-pc kernel: smpboot: CPU 4 is now offline
жов 04 15:27:04 roman-pc kernel: smpboot: CPU 5 is now offline
жов 04 15:27:04 roman-pc kernel: smpboot: CPU 6 is now offline
жов 04 15:27:04 roman-pc kernel: smpboot: CPU 7 is now offline
жов 04 15:27:04 roman-pc kernel: smpboot: CPU 8 is now offline
жов 04 15:27:04 roman-pc kernel: smpboot: CPU 9 is now offline
жов 04 15:27:04 roman-pc kernel: smpboot: CPU 10 is now offline
жов 04 15:27:04 roman-pc kernel: smpboot: CPU 11 is now offline
жов 04 15:27:04 roman-pc kernel: ACPI: Low-level resume complete
жов 04 15:27:04 roman-pc kernel: ACPI: EC: EC started
жов 04 15:27:04 roman-pc kernel: PM: Restoring platform NVS memory
жов 04 15:27:04 roman-pc kernel: Enabling non-boot CPUs ...
жов 04 15:27:04 roman-pc kernel: x86: Booting SMP configuration:
жов 04 15:27:04 roman-pc kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
жов 04 15:27:04 roman-pc kernel: CPU1 is up
жов 04 15:27:04 roman-pc kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
жов 04 15:27:04 roman-pc kernel: CPU2 is up
жов 04 15:27:04 roman-pc kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
жов 04 15:27:04 roman-pc kernel: CPU3 is up
жов 04 15:27:04 roman-pc kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
жов 04 15:27:04 roman-pc kernel: CPU4 is up
жов 04 15:27:04 roman-pc kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
жов 04 15:27:04 roman-pc kernel: CPU5 is up
жов 04 15:27:04 roman-pc kernel: smpboot: Booting Node 0 Processor 6 APIC 0x1
жов 04 15:27:04 roman-pc kernel: CPU6 is up
жов 04 15:27:04 roman-pc kernel: smpboot: Booting Node 0 Processor 7 APIC 0x3
жов 04 15:27:04 roman-pc kernel: CPU7 is up
жов 04 15:27:04 roman-pc kernel: smpboot: Booting Node 0 Processor 8 APIC 0x5
жов 04 15:27:04 roman-pc kernel: CPU8 is up
жов 04 15:27:04 roman-pc kernel: smpboot: Booting Node 0 Processor 9 APIC 0x7
жов 04 15:27:04 roman-pc kernel: CPU9 is up
жов 04 15:27:04 roman-pc kernel: smpboot: Booting Node 0 Processor 10 APIC 0x9
жов 04 15:27:04 roman-pc kernel: CPU10 is up
жов 04 15:27:04 roman-pc kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb
жов 04 15:27:04 roman-pc kernel: CPU11 is up
жов 04 15:27:04 roman-pc kernel: ACPI: Waking up from system sleep state S3
жов 04 15:27:04 roman-pc kernel: ACPI: EC: interrupt unblocked
жов 04 15:27:04 roman-pc kernel: ACPI: EC: event unblocked
жов 04 15:27:04 roman-pc kernel: sd 0:0:0:0: [sda] Starting disk
жов 04 15:27:04 roman-pc kernel: sd 1:0:0:0: [sdb] Starting disk
жов 04 15:27:04 roman-pc kernel: r8169 0000:3b:00.0 enp59s0: Link is Down
жов 04 15:27:04 roman-pc kernel: usb 1-2: reset full-speed USB device number 10 using xhci_hcd
жов 04 15:27:04 roman-pc kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
жов 04 15:27:04 roman-pc kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
жов 04 15:27:04 roman-pc kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
жов 04 15:27:04 roman-pc kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
жов 04 15:27:04 roman-pc kernel: ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
жов 04 15:27:04 roman-pc kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
жов 04 15:27:04 roman-pc kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
жов 04 15:27:04 roman-pc kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
жов 04 15:27:04 roman-pc kernel: ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
жов 04 15:27:04 roman-pc kernel: ata2.00: configured for UDMA/133
жов 04 15:27:04 roman-pc kernel: usb 1-6: reset high-speed USB device number 4 using xhci_hcd
жов 04 15:27:04 roman-pc kernel: usb 1-5: reset high-speed USB device number 3 using xhci_hcd
жов 04 15:27:04 roman-pc kernel: acpi LNXPOWER:05: Turning OFF
жов 04 15:27:04 roman-pc kernel: acpi LNXPOWER:01: Turning OFF
жов 04 15:27:04 roman-pc kernel: OOM killer enabled.
жов 04 15:27:04 roman-pc kernel: Restarting tasks ... 
жов 04 15:27:04 roman-pc kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
жов 04 15:27:04 roman-pc kernel: done.
жов 04 15:27:04 roman-pc systemd-resolved[1653]: Clock change detected. Flushing caches.
жов 04 15:27:04 roman-pc NetworkManager[1666]: <info>  [1633350424.0748] device (enp59s0): state change: disconnected -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
жов 04 15:27:04 roman-pc systemd-logind[1669]: Lid opened.
жов 04 15:27:04 roman-pc kernel: thermal thermal_zone7: failed to read out thermal zone (-61)
жов 04 15:27:04 roman-pc upowerd[2128]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2
жов 04 15:27:04 roman-pc upowerd[2128]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-6
жов 04 15:27:04 roman-pc upowerd[2128]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2
жов 04 15:27:04 roman-pc upowerd[2128]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-6
жов 04 15:27:04 roman-pc systemd-sleep[141363]: System returned from sleep state.
жов 04 15:27:04 roman-pc kernel: PM: suspend exit
жов 04 15:27:04 roman-pc rtkit-daemon[1836]: Supervising 10 threads of 6 processes of 1 users.
жов 04 15:27:04 roman-pc rtkit-daemon[1836]: Successfully made thread 141594 of process 1832 owned by '1000' RT at priority 5.
жов 04 15:27:04 roman-pc rtkit-daemon[1836]: Supervising 11 threads of 6 processes of 1 users.
жов 04 15:27:05 roman-pc systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
жов 04 15:27:05 roman-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
жов 04 15:27:05 roman-pc kernel: audit: type=1131 audit(1633350425.229:626): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
жов 04 15:27:05 roman-pc kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
жов 04 15:27:05 roman-pc systemd[1]: Starting autorandr execution hook...
жов 04 15:27:06 roman-pc kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
жов 04 15:27:06 roman-pc kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
жов 04 15:27:06 roman-pc kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
жов 04 15:27:06 roman-pc kernel: ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
жов 04 15:27:06 roman-pc kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
жов 04 15:27:06 roman-pc kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
жов 04 15:27:06 roman-pc kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
жов 04 15:27:06 roman-pc kernel: ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
жов 04 15:27:06 roman-pc kernel: ata1.00: configured for UDMA/133
жов 04 15:27:06 roman-pc plasmashell[141207]: org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.hdmi-stereo"
жов 04 15:27:06 roman-pc NetworkManager[1666]: <info>  [1633350426.3213] device (enp59s0): carrier: link connected
жов 04 15:27:06 roman-pc NetworkManager[1666]: <info>  [1633350426.3214] device (enp59s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
жов 04 15:27:06 roman-pc kernel: r8169 0000:3b:00.0 enp59s0: Link is Up - 1Gbps/Full - flow control off
жов 04 15:27:06 roman-pc systemd[1]: systemd-suspend.service: Deactivated successfully.
жов 04 15:27:06 roman-pc systemd[1]: Finished System Suspend.
жов 04 15:27:06 roman-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
жов 04 15:27:06 roman-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
жов 04 15:27:06 roman-pc systemd[1]: Stopped target Sleep.
жов 04 15:27:06 roman-pc systemd[1]: Reached target Suspend.
жов 04 15:27:06 roman-pc systemd-logind[1669]: Operation 'sleep' finished.
жов 04 15:27:06 roman-pc kernel: audit: type=1130 audit(1633350426.466:627): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
жов 04 15:27:06 roman-pc kernel: audit: type=1131 audit(1633350426.466:628): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
жов 04 15:27:06 roman-pc kernel: r8169 0000:3b:00.0 enp59s0: Link is Down
жов 04 15:27:06 roman-pc NetworkManager[1666]: <info>  [1633350426.4698] manager: sleep: wake requested (sleeping: yes  enabled: yes)
жов 04 15:27:06 roman-pc ModemManager[1716]: <info>  [sleep-monitor] system is resuming
жов 04 15:27:06 roman-pc NetworkManager[1666]: <info>  [1633350426.4698] device (enp59s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
жов 04 15:27:06 roman-pc NetworkManager[1666]: <info>  [1633350426.4781] device (enp59s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
жов 04 15:27:06 roman-pc plasmashell[141207]: org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.hdmi-stereo"
жов 04 15:27:06 roman-pc systemd[1]: Starting Plasma Restart Service...
жов 04 15:27:06 roman-pc systemd[1]: Stopped target Suspend.
жов 04 15:27:06 roman-pc kernel: Generic FE-GE Realtek PHY r8169-0-3b00:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-0-3b00:00, irq=IGNORE)
жов 04 15:27:06 roman-pc kded5[1924]: bluedevil: About to resume
жов 04 15:27:06 roman-pc NetworkManager[1666]: <info>  [1633350426.6709] device (wlo1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
жов 04 15:27:06 roman-pc NetworkManager[1666]: <info>  [1633350426.6714] device (p2p-dev-wlo1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
жов 04 15:27:06 roman-pc NetworkManager[1666]: <info>  [1633350426.6717] manager: NetworkManager state is now CONNECTED_LOCAL
жов 04 15:27:06 roman-pc kernel: r8169 0000:3b:00.0 enp59s0: Link is Down
жов 04 15:27:06 roman-pc dbus-daemon[1665]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.490' (uid=0 pid=141723 comm="sudo -Hiu roman pkill -ABRT plasmashell ")
жов 04 15:27:06 roman-pc dbus-daemon[1665]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
жов 04 15:27:06 roman-pc sudo[141723]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
жов 04 15:27:06 roman-pc audit[141723]: USER_ACCT pid=141723 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="roman" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
жов 04 15:27:06 roman-pc audit[141723]: CRED_REFR pid=141723 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="roman" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
жов 04 15:27:06 roman-pc sudo[141723]:    roman : PWD=/home/roman ; USER=roman ; COMMAND=/bin/bash --login -c pkill -ABRT plasmashell
жов 04 15:27:06 roman-pc audit[141723]: USER_START pid=141723 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="roman" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
жов 04 15:27:06 roman-pc sudo[141723]: pam_unix(sudo:session): session opened for user roman(uid=1000) by (uid=1000)
жов 04 15:27:06 roman-pc kernel: audit: type=1101 audit(1633350426.676:629): pid=141723 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="roman" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
жов 04 15:27:06 roman-pc kernel: audit: type=1110 audit(1633350426.676:630): pid=141723 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="roman" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
жов 04 15:27:06 roman-pc kernel: audit: type=1105 audit(1633350426.676:631): pid=141723 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="roman" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
жов 04 15:27:06 roman-pc sudo[141723]: pam_unix(sudo:session): session closed for user roman
жов 04 15:27:06 roman-pc audit[141723]: USER_END pid=141723 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="roman" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
жов 04 15:27:06 roman-pc audit[141723]: CRED_DISP pid=141723 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="roman" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
жов 04 15:27:06 roman-pc systemd[1]: Finished Plasma Restart Service.
жов 04 15:27:06 roman-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plasma-restart@roman comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
жов 04 15:27:06 roman-pc systemd[1]: plasma-restart@roman.service: Deactivated successfully.
жов 04 15:27:06 roman-pc systemd[1]: Stopped Plasma Restart Service.
жов 04 15:27:06 roman-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plasma-restart@roman comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
жов 04 15:27:06 roman-pc systemd[1]: Removed slice User Slice of UID roman.
жов 04 15:27:06 roman-pc kernel: audit: type=1106 audit(1633350426.706:632): pid=141723 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="roman" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
жов 04 15:27:06 roman-pc kernel: audit: type=1104 audit(1633350426.706:633): pid=141723 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="roman" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
жов 04 15:27:06 roman-pc kernel: audit: type=1130 audit(1633350426.706:634): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plasma-restart@roman comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
жов 04 15:27:06 roman-pc kernel: audit: type=1131 audit(1633350426.706:635): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plasma-restart@roman comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
жов 04 15:27:07 roman-pc kwin_x11[1930]: kwin_core: XCB error: 10 (BadAccess), sequence: 53342, resource id: 606, major code: 142 (Composite), minor code: 2 (RedirectSubwindows)
жов 04 15:27:07 roman-pc kwin_x11[1930]: DesktopGridConfig::instance called after the first use - ignoring
жов 04 15:27:07 roman-pc autorandr[141598]: Config already loaded
жов 04 15:27:07 roman-pc autorandr[141598]: autorandr running as user roman (started from batch instance)
жов 04 15:27:07 roman-pc autorandr[141598]: hdmi (detected) (current)
жов 04 15:27:07 roman-pc autorandr[141596]: Running autorandr as roman for display :0
жов 04 15:27:07 roman-pc systemd[1]: autorandr.service: Deactivated successfully.
жов 04 15:27:07 roman-pc systemd[1]: Finished autorandr execution hook.
жов 04 15:27:07 roman-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=autorandr comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
жов 04 15:27:07 roman-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=autorandr comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
жов 04 15:27:07 roman-pc audit[141207]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 pid=141207 comm="plasmashell" exe="/usr/bin/plasmashell" sig=6 res=1
жов 04 15:27:07 roman-pc audit: BPF prog-id=93 op=LOAD
жов 04 15:27:07 roman-pc audit: BPF prog-id=94 op=LOAD
жов 04 15:27:07 roman-pc audit: BPF prog-id=95 op=LOAD
жов 04 15:27:07 roman-pc systemd[1]: Started Process Core Dump (PID 141746/UID 0).
жов 04 15:27:07 roman-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@13-141746-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
жов 04 15:27:08 roman-pc plasmashell[141745]: kf.plasma.quick: Applet preload policy set to 1
жов 04 15:27:08 roman-pc kwin_x11[1930]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 53900, resource id: 134217846, major code: 20 (GetProperty), minor code: 0
жов 04 15:27:08 roman-pc kwin_x11[1930]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 53901, resource id: 134217742, major code: 15 (QueryTree), minor code: 0
жов 04 15:27:08 roman-pc kwin_x11[1930]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 53924, resource id: 134217756, major code: 15 (QueryTree), minor code: 0
жов 04 15:27:08 roman-pc kwin_x11[1930]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 53998, resource id: 134217846, major code: 15 (QueryTree), minor code: 0
жов 04 15:27:08 roman-pc kwin_x11[1930]: GlideConfig::instance called after the first use - ignoring
жов 04 15:27:08 roman-pc kwin_x11[1930]: KscreenConfig::instance called after the first use - ignoring
жов 04 15:27:08 roman-pc kwin_x11[1930]: PresentWindowsConfig::instance called after the first use - ignoring
жов 04 15:27:08 roman-pc kcminit[141778]: Initializing  "kcm_mouse" :  "kcminit_mouse"
жов 04 15:27:08 roman-pc ModemManager[1716]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.3': not supported by any plugin
жов 04 15:27:08 roman-pc ModemManager[1716]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1d.0/0000:3b:00.0': not supported by any plugin
жов 04 15:27:09 roman-pc kwin_x11[1930]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 54191, resource id: 127926276, major code: 18 (ChangeProperty), minor code: 0
жов 04 15:27:09 roman-pc kwin_x11[1930]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 54212, resource id: 127926277, major code: 18 (ChangeProperty), minor code: 0
жов 04 15:27:09 roman-pc kwin_x11[1930]: SlideConfig::instance called after the first use - ignoring
жов 04 15:27:09 roman-pc kwin_x11[1930]: SlidingPopupsConfig::instance called after the first use - ignoring
жов 04 15:27:09 roman-pc kwin_x11[1930]: ThumbnailAsideConfig::instance called after the first use - ignoring
жов 04 15:27:09 roman-pc plasmashell[141745]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:56:5: QML MouseArea: Cannot anchor to an item that isn't a parent or sibling.
жов 04 15:27:09 roman-pc plasmashell[141745]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:54: TypeError: Cannot read property 'length' of undefined
жов 04 15:27:09 roman-pc kcminit[141789]: Initializing  "kcm_mouse" :  "kcminit_mouse"
жов 04 15:27:09 roman-pc plasmashell[141745]: kf.kirigami: Units.devicePixelRatio is deprecated (since 5.86 ): This returns 1 when using Qt HiDPI scaling.
жов 04 15:27:09 roman-pc plasmashell[141745]: trying to show an empty dialog
жов 04 15:27:09 roman-pc plasmashell[141745]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height"
жов 04 15:27:09 roman-pc plasmashell[141745]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height"
жов 04 15:27:09 roman-pc plasmashell[141745]: libpng warning: iCCP: known incorrect sRGB profile
жов 04 15:27:09 roman-pc plasmashell[141745]: Plasma Shell startup completed

From the above fragment the only entries that seem to be related to mouse device state are:

жов 04 15:27:04 roman-pc kernel: usb 1-2: reset full-speed USB device number 10 using xhci_hcd
...
жов 04 15:27:08 roman-pc kcminit[141778]: Initializing  "kcm_mouse" :  "kcminit_mouse"

But I couldn’t recognize something wrong (which could hurt the mouse) from that log.

9

It was an idea of not is exactly wrong/suspicious, but to get into settings of such components also.
I would learn the xhci_hcd kernel module and the kcminit OS component modes and all their possible settings. Also would try to realize what is that kcm_mouse, kcminit_mouse, where they are from, their specs and by what it could be used to get the device back from suspended mode other than that “commands”/“function calls”.

$ pacman -Qo kcminit
/usr/bin/kcminit is owned by plasma-workspace 5.22.5-2

Besides of earlier posted idea of to completely prevent USB ports from suspending I would try to introduce a small 1-5 seconds delay to initialize mouse device or USB ports after delay.

I do not know further action what I would do after that, but that try of learning could bring some further ways to point of how to: do not suspend USB mouse device / USB ports or to setup a mode of waking it up back (research of parameters available and to try to introduce a delay).

Also there is some change that BIOS/UEFI update or/and mouse FW update could fix the issue.

Running out of ideas, if I were you, I would try a raw research: to learn and to test each possibly-related mode and setting of all possibly related components which could affect the mouse work. But it can consume much time for doing that, not a fast and easy way w/ unknown final result.

May be some other people have an idea of more clear way of possible solution.

10

Possibly related:
https://forum.manjaro.org/t/usb-ports-of-keyboard-and-mouse-stop-working-after-inactivity/92438

If that not helps, we will try to call @anon89812132 here.

11

Tried that, did not help.