Mouse click not working

Ask Fedora
,
1

Since the last update I experience strange problems with my mouse that drive me insane but i just cant fix or even really debug. More or less at random I my mouse clicks or hovers don’t work anymore, movement is still possible without a problem.

E.g I do something in Firefox, move the mouse outside of the window, only get the resize icon, even tho i am far past the edge of the window. At this point i can only click things inside Firefox and not outside. By pressing meta i “plop” out of Firefox and cant click anything anymore. Also happens with other Programs and not just Firefox

My fix so far is switching to another virtual desktop and back, which fixes the Problem for the moment but is still really annoying..

Maybe someone else has an idea what i could try, look at, fix…

Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.1
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1
Kernel Version: 7.0.13-200.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 32 GiB of RAM (31.2 GiB usable)
Graphics Processor: AMD Radeon RX 6950 XT
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7C37
System Version: 1.0
3

Have a look in the user and system journals for clues.
Maybe you will see errors from the mouse?

4

At least i dont see anything obvious, the problems occured somewhere between the last two entries 14:03:32 ->14:04:54

Jun 28 14:02:08 ryzen-3900x audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-makecache comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? a>
Jun 28 14:02:08 ryzen-3900x audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-makecache comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? ad>
Jun 28 14:02:08 ryzen-3900x systemd[1]: dnf-makecache.service: Consumed 704ms CPU time over 740ms wall clock time, 384M memory peak.
Jun 28 14:03:31 ryzen-3900x systemd[3529]: Started app-org.kde.konsole@f19c9c2e3f264947a7747316b451c1f6.service - Konsole - Terminal.
Jun 28 14:03:31 ryzen-3900x systemd[3529]: Started app-org.kde.konsole-60591.scope.
Jun 28 14:03:31 ryzen-3900x kernel: evm: overlay not supported
Jun 28 14:03:31 ryzen-3900x podman[60659]: 2026-06-28 14:03:31.933691559 +0200 CEST m=+0.169720632 system refresh
Jun 28 14:03:31 ryzen-3900x systemd[3529]: Created slice user.slice - Slice /user.
Jun 28 14:03:31 ryzen-3900x systemd[3529]: Started podman-pause-a6e1c9f4.scope.
Jun 28 14:03:31 ryzen-3900x systemd[3529]: Started podman-pause-c1fb99f9.scope.
Jun 28 14:03:32 ryzen-3900x systemd[3529]: Started podman-pause-190e4598.scope.
Jun 28 14:03:32 ryzen-3900x systemd[3529]: Started podman-pause-4c0fe44a.scope.
Jun 28 14:04:54 ryzen-3900x kwin_wayland[3848]: atomic commit failed: Permission denied
5

What type of mouse? Wired? Wireless?
Do you have another mouse that you can test with?

6

I’d try KWIN_DRM_NO_AMS=1:

echo 'export KWIN_DRM_NO_AMS=1' | sudo tee '/etc/profile.d/kwin-tweaks.sh'
7

Dont have another mouse to test. Tho it does not feel like a hardware problem, moving it still works without any issue. Its a MX Master Vertical

8

Did that, not entirely sure what to expect from it tho?

9

Something with cursor planes (I’ve heard of cursor oddities on AMDGPU with DRM and disabling seems a usual fix GNOME and KDE)

I think it disables having the cursor on a plane(?) by the GPU/its DRM system, and reverts to traditional positioning. On GNOME disabling it made my mouse more consistent, but if your mouse movement was already ok you might not notice a difference (I’d try it for a bit and see if mouse clicks stop working)