Mouse not correctly recognized during boot

Antares2619 · 2026-03-15 11:29:26

Issue
I use a wireless 2.4Ghz USB mouse with an up-to-date Arch system. The mouse used to work as expected in wireless mode for several weeks, but starting few days ago, the cursor became unresponsive when entering KDE after system boot, as if the mouse and the 2.4Ghz dongle were not communicating.

Debugging

The cursor works as expected inside the motherboard UEFI.
The cursor works as expected in the desktop environment after I unplug and replug the 2.4Ghz dongle.
Below, I compare dmesg output at boot for the mouse (and wireless keyboard with separate dongle) with the same output for the mouse if I plug its 2.4Ghz dongle after boot. The printed serial number for the mouse is different in the two cases, and the serial number printed at boot seems wrong and varies too.

At boot (for mouse and keyboard cause of overlap):

    0.956047] usb 3-4: new full-speed USB device number 2 using xhci_hcd
[    0.962790] ata1: SATA link down (SStatus 0 SControl 330)
[    1.009044] usb 1-3: new full-speed USB device number 2 using xhci_hcd
[    1.105239] usb 3-4: New USB device found, idVendor=0b05, idProduct=1a94, bcdDevice= 6.02
[    1.105242] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.105245] usb 3-4: Product: ROG HARPE ACE AIM LAB EDITION
[    1.105247] usb 3-4: Manufacturer: ASUSTeK
[    1.105248] usb 3-4: SerialNumber: NAMPGDD09721\xc2\x9c\x17
[    1.127370] hid-generic 0003:0B05:1A94.0001: hiddev96,hidraw0: USB HID v1.11 Device [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:2d:00.3-4/input0
[    1.135349] input: ASUSTeK ROG HARPE ACE AIM LAB EDITION as /devices/pci0000:00/0000:00:08.1/0000:2d:00.3/usb3/3-4/3-4:1.1/0003:0B05:1A94.0002/input/input2
[    1.135404] hid-generic 0003:0B05:1A94.0002: input,hidraw1: USB HID v1.11 Mouse [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:2d:00.3-4/input1
[    1.143375] input: ASUSTeK ROG HARPE ACE AIM LAB EDITION Consumer Control as /devices/pci0000:00/0000:00:08.1/0000:2d:00.3/usb3/3-4/3-4:1.2/0003:0B05:1A94.0003/input/input3
[    1.194099] input: ASUSTeK ROG HARPE ACE AIM LAB EDITION System Control as /devices/pci0000:00/0000:00:08.1/0000:2d:00.3/usb3/3-4/3-4:1.2/0003:0B05:1A94.0003/input/input4
[    1.194147] input: ASUSTeK ROG HARPE ACE AIM LAB EDITION as /devices/pci0000:00/0000:00:08.1/0000:2d:00.3/usb3/3-4/3-4:1.2/0003:0B05:1A94.0003/input/input5
[    1.194199] input: ASUSTeK ROG HARPE ACE AIM LAB EDITION Keyboard as /devices/pci0000:00/0000:00:08.1/0000:2d:00.3/usb3/3-4/3-4:1.2/0003:0B05:1A94.0003/input/input6
[    1.194284] hid-generic 0003:0B05:1A94.0003: input,hiddev97,hidraw2: USB HID v1.11 Keyboard [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:2d:00.3-4/input2
[    1.274780] ata2: SATA link down (SStatus 0 SControl 330)
[    1.378508] usb 1-3: New USB device found, idVendor=0b05, idProduct=193e, bcdDevice= 3.04
[    1.378514] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    1.378516] usb 1-3: Product: ROG FALCHION
[    1.378518] usb 1-3: Manufacturer: ASUSTeK
[    1.404662] input: ASUSTeK ROG FALCHION as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.0/0003:0B05:193E.0004/input/input7
[    1.455761] hid-generic 0003:0B05:193E.0004: input,hidraw3: USB HID v1.11 Keyboard [ASUSTeK ROG FALCHION] on usb-0000:02:00.0-3/input0
[    1.460628] hid-generic 0003:0B05:193E.0005: hiddev98,hidraw4: USB HID v1.11 Device [ASUSTeK ROG FALCHION] on usb-0000:02:00.0-3/input1
[    1.470419] input: ASUSTeK ROG FALCHION Consumer Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.2/0003:0B05:193E.0006/input/input8
[    1.521609] input: ASUSTeK ROG FALCHION System Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.2/0003:0B05:193E.0006/input/input9
[    1.521665] input: ASUSTeK ROG FALCHION as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.2/0003:0B05:193E.0006/input/input10
[    1.521718] input: ASUSTeK ROG FALCHION Mouse as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.2/0003:0B05:193E.0006/input/input11
[    1.521798] hid-generic 0003:0B05:193E.0006: input,hiddev99,hidraw5: USB HID v1.11 Mouse [ASUSTeK ROG FALCHION] on usb-0000:02:00.0-3/input2
[    1.525324] input: ASUSTeK ROG FALCHION as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.3/0003:0B05:193E.0007/input/input12
[    1.576597] hid-generic 0003:0B05:193E.0007: input,hidraw6: USB HID v1.11 Keyboard [ASUSTeK ROG FALCHION] on usb-0000:02:00.0-3/input3
[    1.589892] ata3: SATA link down (SStatus 0 SControl 330)

After boot (for mouse):

[  311.967559] usb 3-4: new full-speed USB device number 3 using xhci_hcd
[  312.117262] usb 3-4: New USB device found, idVendor=0b05, idProduct=1a94, bcdDevice= 6.02
[  312.117268] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  312.117270] usb 3-4: Product: ROG HARPE ACE AIM LAB EDITION
[  312.117272] usb 3-4: Manufacturer: ASUSTeK
[  312.117274] usb 3-4: SerialNumber: NAMPGDD09721
[  312.139425] hid-generic 0003:0B05:1A94.0009: hiddev96,hidraw0: USB HID v1.11 Device [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:2d:00.3-4/input0
[  312.147373] input: ASUSTeK ROG HARPE ACE AIM LAB EDITION as /devices/pci0000:00/0000:00:08.1/0000:2d:00.3/usb3/3-4/3-4:1.1/0003:0B05:1A94.000A/input/input26
[  312.147489] hid-generic 0003:0B05:1A94.000A: input,hidraw1: USB HID v1.11 Mouse [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:2d:00.3-4/input1
[  312.155397] input: ASUSTeK ROG HARPE ACE AIM LAB EDITION Consumer Control as /devices/pci0000:00/0000:00:08.1/0000:2d:00.3/usb3/3-4/3-4:1.2/0003:0B05:1A94.000B/input/input27
[  312.205755] input: ASUSTeK ROG HARPE ACE AIM LAB EDITION System Control as /devices/pci0000:00/0000:00:08.1/0000:2d:00.3/usb3/3-4/3-4:1.2/0003:0B05:1A94.000B/input/input28
[  312.205835] input: ASUSTeK ROG HARPE ACE AIM LAB EDITION as /devices/pci0000:00/0000:00:08.1/0000:2d:00.3/usb3/3-4/3-4:1.2/0003:0B05:1A94.000B/input/input29
[  312.205901] input: ASUSTeK ROG HARPE ACE AIM LAB EDITION Keyboard as /devices/pci0000:00/0000:00:08.1/0000:2d:00.3/usb3/3-4/3-4:1.2/0003:0B05:1A94.000B/input/input30
[  312.206012] hid-generic 0003:0B05:1A94.000B: input,hiddev97,hidraw2: USB HID v1.11 Keyboard [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:2d:00.3-4/input2

Last edited by Antares2619 (2026-03-15 13:05:34)

seth · 2026-03-15 14:19:36

The cursor works as expected in the desktop environment after I unplug and replug the 2.4Ghz dongle.

https://wiki.archlinux.org/title/Power_ … utosuspend
Though because of

the cursor became unresponsive when entering KDE after system boot

this could also be powerdevil

Below, I compare dmesg output at boot for the mouse

Random isolated lines from dmesg (the second set just shows the dongle being recognized, it's way too late to explain why it would not work before; the first one ends 1.5s into the boot, so likely way before you log into KDE) won't help anything here.

Antares2619 · 2026-03-15 19:33:36

I have added a udev rule to blacklist the mouse from autosuspend. Below is where I looked for verification:

$ cat /sys/bus/usb/devices/3-4/product
ROG HARPE ACE AIM LAB EDITION
$ cat /sys/bus/usb/devices/3-4/idProduct
1a94
$ cat /sys/bus/usb/devices/3-4/idVendor
0b05
$ cat /sys/bus/usb/devices/3-4/power/autosuspend
-1

Unfortunately this change did not solve the issue. I will try to look further into power management and powerdevil.

seth wrote:

Random isolated lines from dmesg (the second set just shows the dongle being recognized, it's way too late to explain why it would not work before; the first one ends 1.5s into the boot, so likely way before you log into KDE) won't help anything here.

For clarity, the sequence of events is the following:

The system starts booting with dongle plugged and mouse ON. This is when the kernel prints the first set.
The system starts the desktop environment.
I verify that the cursor is not responsive.
I unplug and re-plug the dongle. This is when the kernel prints the second set.
I verify that the cursor is responsive.

Anyway I am posting the entire dmesg output of a similar session where I replicated the same sequence of events. Perhaps it's more helpful: https://pastebin.com/mwkdpN6A

Last edited by Antares2619 (2026-03-15 19:37:22)

seth · 2026-03-15 21:38:21

The system journal for the boot will put this into userspace context

sudo journalctl -b | curl -F 'file=@-' 0x0.st

[   16.920906] warning: `conky' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[   39.650296] usb 3-4: USB disconnect, device number 2
[   42.159841] usb 3-4: new full-speed USB device number 3 using xhci_hcd

17s in conky starts (indicating your session?), 24s later the dongle disconnects (likely you pulling it), 3s later it's plugged back.

The system starts the desktop environment.

Do you autologin? Does the mouse work before your start the GUI session (either in the DM or you can test "evtest" or "libinput debug-events" on the console)

Do you use any bluetooth devices?
Can you disable the BT chip? (It will operate on the same radio band as the dongle)

Is this a dual-boot system (ie. is there a parallel windows)?

Antares2619 · 2026-03-16 12:02:17

I think we are making progress The mouse input seems to reach the OS, but for some reason it is not reflected on the cursor.

The mouse seems to work in tty according to evtest, and evtest also shows mouse inputs being received correctly at boot in Alacritty inside KDE! However, the cursor won't move neither in KDE nor in the DM (plasma login) until I unplug and replug the dongle...
Here is journalctl following the same 1-5 sequence of events from my previous post. To answer the rest, yes I normally use autologin and I disabled it while testing with evtest. I keep bluetooth and wlan disabled by default through rfkill. And no dual boot, but the mouse works as expected in a different computer with windows.

Last edited by Antares2619 (2026-03-16 14:25:45)

seth · 2026-03-16 14:28:24

What if you only start the multi-user.target 2nd link below) and
1. explicitly start plasmalogin from there
2. start kde manually, https://wiki.archlinux.org/title/KDE#From_the_console
3. startx some X11 session (openbox or naked X11 server will do - we only care whether the mouse moves)

Antares2619 · 2026-03-16 19:35:07

I booted into TTY and tried the different cases below. In all of those cases, the mouse pointer did not move until I unplugged and replugged the dongle.

1) Plasmalogin from TTY:

$ sudo systemctl start plasmalogin

2) Plasma/Wayland from TTY:

$ /usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland

3) Plasma/X11 from TTY (I have also tried a minimal X11 case with openbox):

$ sudo pacman -Sy xorg-server xorg-xinit openbox
$ echo "export DESKTOP_SESSION=plasma
exec startplasma-x11" > ~/.xinitrc
$ startx

###
On a side note, this might be nothing, but it still seems strange to me that this line during boot:

[1.105248] usb 3-4: SerialNumber: NAMPGDD09721\xc2\x9c\x17

becomes this second line when I unplug and replug the dongle after boot:

[312.117274] usb 3-4: SerialNumber: NAMPGDD09721

And that difference is more starking in journalctl, where that first line is reported as:

archlinux kernel: [38B blob data]

Last edited by Antares2619 (2026-03-16 20:00:12)

seth · 2026-03-16 20:33:41

On a side note, this might be nothing, but it still seems strange to me that this line during boot:

That's usually a sign that the controller hasn't fully/properly initialized when the device is probed - do you have this (and the symptoms) also on warm boots (reboot w/o powering off)
Can you try the dongle in a different slot?

Plasma/X11 from TTY (I have also tried a minimal X11 case with openbox):

And please post your ~/.local/share/xorg/Xorg.0.log

Antares2619 · 2026-03-17 17:24:53

That's usually a sign that the controller hasn't fully/properly initialized when the device is probed - do you have this (and the symptoms) also on warm boots (reboot w/o powering off)
Can you try the dongle in a different slot?

The dongle is usually in the front panel. I just tried a USB port in the back panel with same result. I have the same result also during warm boots.

And please post your ~/.local/share/xorg/Xorg.0.log

The log prints some error about the mouse starting at [768.826] as x11 initializes, and no error later when I remove and insert the dongle. That seems informative to me, but you would know better: https://0x0.st/P9Ke.txt

Last edited by Antares2619 (2026-03-17 17:31:57)

seth · 2026-03-17 20:54:03

There's first some "ASUSTeK ROG FALCHION", then

[   768.827] (EE) libinput: ASUSTeK ROG HARPE ACE AIM LAB EDITION: Failed to create a device for /dev/input/event2
[   768.827] (EE) PreInit returned 2 for "ASUSTeK ROG HARPE ACE AIM LAB EDITION"

and only when you re-plug the device

[   790.371] (II) config/udev: Adding input device ASUSTeK ROG HARPE ACE AIM LAB EDITION (/dev/input/mouse0)
[   790.403] (II) config/udev: Adding input device ASUSTeK ROG HARPE ACE AIM LAB EDITION Consumer Control (/dev/input/event3)
[   790.403] (**) ASUSTeK ROG HARPE ACE AIM LAB EDITION Consumer Control: Applying InputClass "libinput keyboard catchall"
[   790.403] (II) Using input driver 'libinput' for 'ASUSTeK ROG HARPE ACE AIM LAB EDITION Consumer Control'
[   790.404] (**) ASUSTeK ROG HARPE ACE AIM LAB EDITION Consumer Control: always reports core events

so this checks out.

Does https://www.baeldung.com/linux/usb-devi … et-command suffice to make the mouse work in the display server?

Antares2619 · 2026-03-19 21:12:46

It seems no The pointer refuses to move even after I try to reset the device via software. I tried with the 'usbreset', 'sysfs', and 'udevadm' methods in order.

Mar 19 22:08:36 pc-nico sudo[1979]:     nico : TTY=pts/1 ; PWD=/home/nico ; USER=root ; COMMAND=/usr/bin/usbreset 001/002
Mar 19 22:08:36 pc-nico sudo[1979]: pam_unix(sudo:session): session opened for user root(uid=0) by nico(uid=1000)
Mar 19 22:08:36 pc-nico kernel: usb 1-3: reset full-speed USB device number 2 using xhci_hcd
Mar 19 22:08:37 pc-nico sudo[1979]: pam_unix(sudo:session): session closed for user root
Mar 19 22:09:05 pc-nico sudo[2020]:     nico : TTY=pts/1 ; PWD=/home/nico ; USER=root ; COMMAND=/usr/bin/tee /sys/bus/usb/devices/1-3/authorized
Mar 19 22:09:05 pc-nico sudo[2020]: pam_unix(sudo:session): session opened for user root(uid=0) by nico(uid=1000)
Mar 19 22:09:05 pc-nico sudo[2020]: pam_unix(sudo:session): session closed for user root
Mar 19 22:09:10 pc-nico sudo[2033]:     nico : TTY=pts/1 ; PWD=/home/nico ; USER=root ; COMMAND=/usr/bin/tee /sys/bus/usb/devices/1-3/authorized
Mar 19 22:09:10 pc-nico sudo[2033]: pam_unix(sudo:session): session opened for user root(uid=0) by nico(uid=1000)
Mar 19 22:09:10 pc-nico kernel: hid-generic 0003:0B05:1A94.000D: hiddev98,hidraw3: USB HID v1.11 Device [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:02:00.0-3/input0
Mar 19 22:09:10 pc-nico kernel: input: ASUSTeK ROG HARPE ACE AIM LAB EDITION as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.1/0003:0B05:1A94.000E/input/input37
Mar 19 22:09:10 pc-nico kernel: hid-generic 0003:0B05:1A94.000E: input,hidraw4: USB HID v1.11 Mouse [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:02:00.0-3/input1
Mar 19 22:09:10 pc-nico kernel: input: ASUSTeK ROG HARPE ACE AIM LAB EDITION Consumer Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.2/0003:0B05:1A94.000F/input/input38
Mar 19 22:09:10 pc-nico kernel: input: ASUSTeK ROG HARPE ACE AIM LAB EDITION System Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.2/0003:0B05:1A94.000F/input/input39
Mar 19 22:09:10 pc-nico kernel: input: ASUSTeK ROG HARPE ACE AIM LAB EDITION as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.2/0003:0B05:1A94.000F/input/input40
Mar 19 22:09:10 pc-nico kernel: input: ASUSTeK ROG HARPE ACE AIM LAB EDITION Keyboard as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.2/0003:0B05:1A94.000F/input/input41
Mar 19 22:09:10 pc-nico sudo[2033]: pam_unix(sudo:session): session closed for user root
Mar 19 22:09:10 pc-nico kernel: hid-generic 0003:0B05:1A94.000F: input,hiddev99,hidraw5: USB HID v1.11 Keyboard [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:02:00.0-3/input2
Mar 19 22:09:10 pc-nico kernel: usb 1-3: authorized to connect
Mar 19 22:09:10 pc-nico kwin_wayland[909]: Failed to open /dev/input/event9 device (No such device)
Mar 19 22:09:10 pc-nico systemd-logind[747]: Watching system buttons on /dev/input/event10 (ASUSTeK ROG HARPE ACE AIM LAB EDITION Keyboard)
Mar 19 22:09:10 pc-nico kwin_wayland[909]: Failed to open /dev/input/event10 device (No such device)
Mar 19 22:09:10 pc-nico systemd-logind[747]: Watching system buttons on /dev/input/event8 (ASUSTeK ROG HARPE ACE AIM LAB EDITION System Control)
Mar 19 22:09:10 pc-nico kwin_wayland[909]: Failed to open /dev/input/event7 device (No such device)
Mar 19 22:09:10 pc-nico kwin_wayland[909]: Failed to open /dev/input/event8 device (No such device)
Mar 19 22:09:10 pc-nico kwin_wayland[909]: Failed to open /dev/input/event6 device (No such device)
Mar 19 22:09:33 pc-nico sudo[2088]:     nico : TTY=pts/1 ; PWD=/home/nico ; USER=root ; COMMAND=/usr/bin/udevadm trigger --action=add /sys/bus/usb/devices/1-3
Mar 19 22:09:33 pc-nico sudo[2088]: pam_unix(sudo:session): session opened for user root(uid=0) by nico(uid=1000)
Mar 19 22:09:33 pc-nico sudo[2088]: pam_unix(sudo:session): session closed for user root
Mar 19 22:09:33 pc-nico mtp-probe[2093]: checking bus 1, device 2: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3"
Mar 19 22:09:33 pc-nico mtp-probe[2093]: bus: 1, device: 2 was not an MTP device
Mar 19 22:09:33 pc-nico systemd-logind[747]: Watching system buttons on /dev/input/event8 (ASUSTeK ROG HARPE ACE AIM LAB EDITION System Control)
Mar 19 22:09:33 pc-nico kwin_wayland[909]: Failed to open /dev/input/event8 device (No such device)
Mar 19 22:09:33 pc-nico systemd-logind[747]: Watching system buttons on /dev/input/event10 (ASUSTeK ROG HARPE ACE AIM LAB EDITION Keyboard)
Mar 19 22:09:33 pc-nico kwin_wayland[909]: Failed to open /dev/input/event10 device (No such device)
Mar 19 22:09:33 pc-nico kwin_wayland[909]: Failed to open /dev/input/event7 device (No such device)
Mar 19 22:09:33 pc-nico kwin_wayland[909]: Failed to open /dev/input/event9 device (No such device)
Mar 19 22:09:33 pc-nico kwin_wayland[909]: Failed to open /dev/input/event6 device (No such device)

I have the same issue with this mouse on a separate Arch system too. It worked just fine until a couple of weeks ago, so the issue is likely either something broken with the mouse, or a software update somewhere that broke the functionality.

Last edited by Antares2619 (2026-03-20 16:00:09)

seth · 2026-03-20 16:23:03

so the issue is likely either something broken with the mouse, or a software update somewhere that broke the functionality

https://grml.org/

Only writing /sys/bus/usb/devices/1-3/authorized caused a response, what if you only boot the multi-user.target (2nd link below) re-authorize the device and then manually progress to the graphical.target (or start plasma)?

Spike29 · 2026-03-22 18:27:38

Antares2619 wrote:

I have the same issue with this mouse on a separate Arch system too. It worked just fine until a couple of weeks ago, so the issue is likely either something broken with the mouse, or a software update somewhere that broke the functionality.

Hello, I have the exact same issue with an ASUS mouse (ROG Keris ii ace), so I don't think your mouse is broken
None of the solutions you've tried work for me either, except unplugging then re-plugging the mouse. There seems to be a race condition somewhere, as about 10% of the time the mouse works as expected on startup.

I've also tested the mouse dongle on a second PC with Arch Linux + GNOME instead of Plasma, and had no issues 3 boots in a row. So this problem *might* be specific to Plasma.

seth · 2026-03-22 22:43:47

So this problem *might* be specific to Plasma.

Should be easy enough to test?
https://wiki.archlinux.org/title/Deskto … _supported - knock yourself out

Antares2619 · 2026-03-24 19:21:50

Should be easy enough to test?

I have been wanting to open Cosmic for a while, so I took the chance for this test, and no, in my case at least, the mouse cursor is unresponsive with Cosmic too. That's what I expected, because the issue was present also with openbox on x11.

what if you only boot the multi-user.target (2nd link below) re-authorize the device and then manually progress to the graphical.target (or start plasma)?

The cursor remains unresponsive after booting into console, de-authorizing and re-authorizing the usb device, and starting plasmalogin. And yet, evtest always prints correctly the mouse input signals.

Here is an extract of the log starting with me de-authorizing the device, and ending with the window manager unable to find some version of the mouse (event 2 to 6):

Mar 24 20:13:54 pc-nico sudo[981]:     nico : TTY=tty1 ; PWD=/home/nico ; USER=root ; COMMAND=/usr/bin/tee /sys/bus/usb/devices/1-3/authorized
Mar 24 20:13:54 pc-nico sudo[981]: pam_unix(sudo:session): session opened for user root(uid=0) by nico(uid=1000)
Mar 24 20:13:54 pc-nico sudo[981]: pam_unix(sudo:session): session closed for user root
Mar 24 20:14:02 pc-nico sudo[1004]:     nico : TTY=tty1 ; PWD=/home/nico ; USER=root ; COMMAND=/usr/bin/tee /sys/bus/usb/devices/1-3/authorized
Mar 24 20:14:02 pc-nico sudo[1004]: pam_unix(sudo:session): session opened for user root(uid=0) by nico(uid=1000)
Mar 24 20:14:02 pc-nico kernel: hid-generic 0003:0B05:1A94.000A: hiddev96,hidraw0: USB HID v1.11 Device [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:02:00.0-3/input0
Mar 24 20:14:02 pc-nico kernel: input: ASUSTeK ROG HARPE ACE AIM LAB EDITION as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.1/0003:0B05:1A94.000B/input/input29
Mar 24 20:14:02 pc-nico kernel: hid-generic 0003:0B05:1A94.000B: input,hidraw1: USB HID v1.11 Mouse [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:02:00.0-3/input1
Mar 24 20:14:02 pc-nico kernel: input: ASUSTeK ROG HARPE ACE AIM LAB EDITION Consumer Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.2/0003:0B05:1A94.000C/input/input30
Mar 24 20:14:02 pc-nico kernel: input: ASUSTeK ROG HARPE ACE AIM LAB EDITION System Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.2/0003:0B05:1A94.000C/input/input31
Mar 24 20:14:02 pc-nico kernel: input: ASUSTeK ROG HARPE ACE AIM LAB EDITION as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.2/0003:0B05:1A94.000C/input/input32
Mar 24 20:14:02 pc-nico kernel: input: ASUSTeK ROG HARPE ACE AIM LAB EDITION Keyboard as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.2/0003:0B05:1A94.000C/input/input33
Mar 24 20:14:02 pc-nico kernel: hid-generic 0003:0B05:1A94.000C: input,hiddev97,hidraw2: USB HID v1.11 Keyboard [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:02:00.0-3/input2
Mar 24 20:14:02 pc-nico sudo[1004]: pam_unix(sudo:session): session closed for user root
Mar 24 20:14:02 pc-nico kernel: usb 1-3: authorized to connect
Mar 24 20:14:02 pc-nico systemd-logind[774]: Watching system buttons on /dev/input/event6 (ASUSTeK ROG HARPE ACE AIM LAB EDITION Keyboard)
Mar 24 20:14:02 pc-nico systemd-logind[774]: Watching system buttons on /dev/input/event4 (ASUSTeK ROG HARPE ACE AIM LAB EDITION System Control)
Mar 24 20:14:12 pc-nico sudo[1038]:     nico : TTY=tty1 ; PWD=/home/nico ; USER=root ; COMMAND=/usr/bin/systemctl start plasmalogin
Mar 24 20:14:12 pc-nico sudo[1038]: pam_unix(sudo:session): session opened for user root(uid=0) by nico(uid=1000)
Mar 24 20:14:12 pc-nico systemd[1]: Stopping Getty on tty1...
Mar 24 20:14:12 pc-nico login[856]: pam_unix(login:session): session closed for user nico
Mar 24 20:14:12 pc-nico sudo[1038]: pam_unix(sudo:session): session closed for user root
Mar 24 20:14:12 pc-nico systemd[1]: getty@tty1.service: Deactivated successfully.
Mar 24 20:14:12 pc-nico systemd[1]: Stopped Getty on tty1.
Mar 24 20:14:12 pc-nico systemd[1]: session-1.scope: Deactivated successfully.
Mar 24 20:14:12 pc-nico systemd-logind[774]: Session 1 logged out. Waiting for processes to exit.
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/ldac
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSink/aptx_hd
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/aptx_hd
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSink/aptx
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/aptx
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSink/aac
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/aac
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSink/opus_g
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/opus_g
Mar 24 20:14:12 pc-nico systemd[1]: Started Plasma Login Manager.
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSink/sbc
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/sbc
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Mar 24 20:14:12 pc-nico systemd-logind[774]: Removed session 1.
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/faststream
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/faststream_duplex
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSink/opus_05
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/opus_05
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Mar 24 20:14:12 pc-nico bluetoothd[768]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Mar 24 20:14:12 pc-nico systemd[894]: Reached target Sound Card.
Mar 24 20:14:12 pc-nico plasmalogin[1045]: Initializing...
Mar 24 20:14:12 pc-nico plasmalogin[1045]: Starting...
Mar 24 20:14:12 pc-nico plasmalogin[1045]: Logind interface found
Mar 24 20:14:12 pc-nico plasmalogin[1045]: Adding new display...
Mar 24 20:14:12 pc-nico plasmalogin[1045]: Using VT 1
Mar 24 20:14:12 pc-nico plasmalogin[1045]: Display server started.
Mar 24 20:14:12 pc-nico plasmalogin[1045]: Socket server starting...
Mar 24 20:14:12 pc-nico plasmalogin[1045]: Socket server started.
Mar 24 20:14:12 pc-nico plasmalogin[1045]: Greeter starting...
Mar 24 20:14:12 pc-nico plasmalogin-helper[1071]: [PAM] Starting...
Mar 24 20:14:12 pc-nico plasmalogin-helper[1071]: [PAM] Authenticating...
Mar 24 20:14:12 pc-nico plasmalogin-helper[1071]: [PAM] returning.
Mar 24 20:14:12 pc-nico plasmalogin-helper[1071]: pam_unix(plasmalogin-greeter:session): session opened for user plasmalogin(uid=967) by (uid=0)
Mar 24 20:14:12 pc-nico systemd-logind[774]: New session 'c1' of user 'plasmalogin' with class 'greeter' and type 'wayland'.
Mar 24 20:14:12 pc-nico systemd[1]: Created slice User Slice of UID 967.
Mar 24 20:14:12 pc-nico systemd[1]: Starting User Runtime Directory /run/user/967...
Mar 24 20:14:12 pc-nico systemd[1]: Finished User Runtime Directory /run/user/967.
Mar 24 20:14:12 pc-nico systemd[1]: Starting User Manager for UID 967...
Mar 24 20:14:12 pc-nico (systemd)[1074]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[plasmalogin] ruser=[<unknown>] rhost=[<unknown>]
Mar 24 20:14:12 pc-nico (systemd)[1074]: pam_unix(systemd-user:session): session opened for user plasmalogin(uid=967) by plasmalogin(uid=0)
Mar 24 20:14:12 pc-nico systemd-logind[774]: New session '3' of user 'plasmalogin' with class 'manager-early' and type 'unspecified'.
Mar 24 20:14:12 pc-nico systemd[1074]: Queued start job for default target Main User Target.
Mar 24 20:14:12 pc-nico systemd[1074]: Created slice User Application Slice.
Mar 24 20:14:12 pc-nico systemd[1074]: Reached target Paths.
Mar 24 20:14:12 pc-nico systemd[1074]: Reached target Timers.
Mar 24 20:14:12 pc-nico systemd[1074]: Starting D-Bus User Message Bus Socket...
Mar 24 20:14:12 pc-nico systemd[1074]: Listening on GnuPG network certificate management daemon.
Mar 24 20:14:12 pc-nico systemd[1074]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 24 20:14:12 pc-nico systemd[1074]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Mar 24 20:14:12 pc-nico systemd[1074]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Mar 24 20:14:12 pc-nico systemd[1074]: Listening on GnuPG cryptographic agent and passphrase cache.
Mar 24 20:14:12 pc-nico systemd[1074]: Listening on GnuPG public key management service.
Mar 24 20:14:12 pc-nico systemd[1074]: Listening on p11-kit server.
Mar 24 20:14:12 pc-nico systemd[1074]: Listening on PipeWire PulseAudio.
Mar 24 20:14:12 pc-nico systemd[1074]: Listening on PipeWire Multimedia System Sockets.
Mar 24 20:14:12 pc-nico systemd[1074]: Listening on Speech Dispatcher Socket.
Mar 24 20:14:12 pc-nico systemd[1074]: Listening on Query the User Interactively for a Password.
Mar 24 20:14:12 pc-nico systemd[1074]: Listening on Disk Image Download Service Socket.
Mar 24 20:14:12 pc-nico systemd[1074]: Listening on Journal Log Access Socket.
Mar 24 20:14:12 pc-nico systemd[1074]: Listening on Virtual Machine and Container Registration Service Socket.
Mar 24 20:14:12 pc-nico systemd[1074]: Listening on D-Bus User Message Bus Socket.
Mar 24 20:14:12 pc-nico systemd[1074]: Reached target Sockets.
Mar 24 20:14:12 pc-nico systemd[1074]: Reached target Basic System.
Mar 24 20:14:12 pc-nico systemd[1074]: Reached target Main User Target.
Mar 24 20:14:12 pc-nico systemd[1074]: Startup finished in 95ms.
Mar 24 20:14:12 pc-nico systemd[1]: Started User Manager for UID 967.
Mar 24 20:14:12 pc-nico systemd[1]: Started Session c1 of User plasmalogin.
Mar 24 20:14:12 pc-nico plasmalogin-helper[1071]: Starting Wayland user session: "/usr/share/plasmalogin/scripts/wayland-session" "/usr/bin/startplasma-login-wayland"
Mar 24 20:14:12 pc-nico plasmalogin-helper[1083]: Jumping to VT 1
Mar 24 20:14:12 pc-nico plasmalogin-helper[1083]: VT mode fixed
Mar 24 20:14:12 pc-nico plasmalogin[1045]: Greeter session started successfully
Mar 24 20:14:12 pc-nico systemd[1]: Starting Locale Service...
Mar 24 20:14:12 pc-nico systemd[1]: Started Locale Service.
Mar 24 20:14:12 pc-nico systemd[1074]: Created slice User Core Session Slice.
Mar 24 20:14:12 pc-nico systemd[1074]: Starting D-Bus User Message Bus...
Mar 24 20:14:12 pc-nico dbus-broker-launch[1098]: Service file '/usr/share/dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
Mar 24 20:14:12 pc-nico dbus-broker-launch[1098]: Service file '/usr/share/dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
Mar 24 20:14:12 pc-nico dbus-broker-launch[1098]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Mar 24 20:14:12 pc-nico dbus-broker-launch[1098]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Mar 24 20:14:12 pc-nico dbus-broker-launch[1098]: Service file '/usr/share/dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
Mar 24 20:14:12 pc-nico systemd[1074]: Started D-Bus User Message Bus.
Mar 24 20:14:12 pc-nico dbus-broker-launch[1098]: Ready
Mar 24 20:14:12 pc-nico systemd[1074]: Created slice User Background Tasks Slice.
Mar 24 20:14:12 pc-nico systemd[1074]: Starting KDE Window Manager (Login Manager Version)...
Mar 24 20:14:12 pc-nico kwin_wayland[1100]: Failed to gain real time thread priority (See CAP_SYS_NICE in the capabilities(7) man page). error: Operation not permitted
Mar 24 20:14:12 pc-nico kwin_wayland[1100]: No backend specified, automatically choosing drm
Mar 24 20:14:12 pc-nico kwin_wayland[1100]: Accepting client connections on sockets: QList("wayland-0")
Mar 24 20:14:13 pc-nico kwin_wayland[1100]: Failed to gain real time thread priority (See CAP_SYS_NICE in the capabilities(7) man page). error: Operation not permitted
Mar 24 20:14:13 pc-nico kwin_wayland[1100]: Failed to open /dev/input/event2 device (No such device)
Mar 24 20:14:13 pc-nico kwin_wayland[1100]: Failed to open /dev/input/event3 device (No such device)
Mar 24 20:14:13 pc-nico kwin_wayland[1100]: Failed to open /dev/input/event4 device (No such device)
Mar 24 20:14:13 pc-nico kwin_wayland[1100]: Failed to open /dev/input/event5 device (No such device)
Mar 24 20:14:13 pc-nico kwin_wayland[1100]: Failed to open /dev/input/event6 device (No such device)
Mar 24 20:14:13 pc-nico kwin_wayland[1100]: Failed to gain real time thread priority (See CAP_SYS_NICE in the capabilities(7) man page). error: Operation not permitted
Mar 24 20:14:13 pc-nico systemd[1074]: Started KDE Window Manager (Login Manager Version).

Last edited by Antares2619 (2026-03-24 20:43:12)

seth · 2026-03-24 22:28:13

Mar 24 20:14:13 pc-nico kwin_wayland[1100]: Failed to open /dev/input/event2 device (No such device)
Mar 24 20:14:13 pc-nico kwin_wayland[1100]: Failed to open /dev/input/event3 device (No such device)
Mar 24 20:14:13 pc-nico kwin_wayland[1100]: Failed to open /dev/input/event4 device (No such device)
Mar 24 20:14:13 pc-nico kwin_wayland[1100]: Failed to open /dev/input/event5 device (No such device)
Mar 24 20:14:13 pc-nico kwin_wayland[1100]: Failed to open /dev/input/event6 device (No such device)

Likely just permissions

ls -l /dev/input/*

You could try to add yourself to the input group but this should not be necessary and the logs are just noise.
Do you get events in

libinput debug-events

from the dead mouse?
What if you try X11 w/ https://archlinux.org/packages/extra/x8 … put-evdev/ ?

Antares2619 · 2026-03-25 05:19:52

Likely just permissions
ls -l /dev/input/*
You could try to add yourself to the input group but this should not be necessary and the logs are just noise.

I think the input group 2 to 6 exists, and kwin is unable to access it. Here is the output of "ls -l /dev/input/*" with the mouse pointer dead.

Do you get events in
libinput debug-events
from the dead mouse?

Yes, libinput prints events from the mouse similarly to evtest, and typically on "event2".

What if you try X11 w/ https://archlinux.org/packages/extra/x8 … put-evdev/ ?

I will get to this

Last edited by Antares2619 (2026-03-25 05:26:19)

seth · 2026-03-25 08:10:02

Yes, libinput prints events from the mouse similarly to evtest, and typically on "event2".

https://archlinux.org/packages/extra/x8 … put-evdev/ will likely not help - on X11, check the output of

xinput list --name-only

Any device that starts w/ "~" is disabled

Last edited by seth (2026-03-25 08:10:10)

Arch Linux

#1 2026-03-15 11:29:26

Mouse not correctly recognized during boot

#2 2026-03-15 14:19:36

Re: Mouse not correctly recognized during boot

#3 2026-03-15 19:33:36

Re: Mouse not correctly recognized during boot

#4 2026-03-15 21:38:21

Re: Mouse not correctly recognized during boot

#5 2026-03-16 12:02:17

Re: Mouse not correctly recognized during boot

#6 2026-03-16 14:28:24

Re: Mouse not correctly recognized during boot

#7 2026-03-16 19:35:07

Re: Mouse not correctly recognized during boot

#8 2026-03-16 20:33:41

Re: Mouse not correctly recognized during boot

#9 2026-03-17 17:24:53

Re: Mouse not correctly recognized during boot

#10 2026-03-17 20:54:03

Re: Mouse not correctly recognized during boot

#11 2026-03-19 21:12:46

Re: Mouse not correctly recognized during boot

#12 2026-03-20 16:23:03

Re: Mouse not correctly recognized during boot

#13 2026-03-22 18:27:38

Re: Mouse not correctly recognized during boot

#14 2026-03-22 22:43:47

Re: Mouse not correctly recognized during boot

#15 2026-03-24 19:21:50

Re: Mouse not correctly recognized during boot

#16 2026-03-24 22:28:13

Re: Mouse not correctly recognized during boot

#17 2026-03-25 05:19:52

Re: Mouse not correctly recognized during boot

#18 2026-03-25 08:10:02

Re: Mouse not correctly recognized during boot

Board footer