I wonder if it is another case of this problem:
Are there multiple device nodes under /dev/input that are receiving your pointer events? I only have one and my mouse is working fine (on Fedora Linux 40 using Sway).
FWIW, Here is a little script that I put together to automate finding what event devices are receiving pointer events (the “script” is the one-liner command that starts with for ...). You have to run it as root and you need to move your mouse continuously while the for loop iterates over your event device nodes.
[/home/glb]$ sudo dnf install -y evtest
Last metadata expiration check: 0:32:59 ago on Tue 23 Jul 2024 06:03:27 PM UTC.
Package evtest-1.35-7.fc40.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
[/home/glb]$ sudo -i
[/root]# for i in $(ls -v /dev/input/event*); do printf "\e[1mTESTING $i\e[0m:\n"; timeout -s int 3 bash -c "evtest $i | grep -i '^event:' | tr '\n' '\r'"; echo; done
TESTING /dev/input/event0:
TESTING /dev/input/event1:
TESTING /dev/input/event2:
TESTING /dev/input/event3:
TESTING /dev/input/event4:
TESTING /dev/input/event5:
TESTING /dev/input/event6:
Event: time 1721759399.307444, -------------L), code 1 (REL_Y), value 144
TESTING /dev/input/event7:
TESTING /dev/input/event8:
TESTING /dev/input/event9:
[/root]# logout
[/home/glb]$
In the above example, only /dev/input/event6 showed that it was receiving events as I was moving my mouse pointer.