Cursor seems to chronically lag for 15 seconds and not work after opening the tiling manager for the first time

Ask Fedora
, ,
1

FIxed:

KWIN_DRM_NO_AMS=1

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

-------

After learning that the tiling manager (meta+T) is apparently useful and cool, I opened it and dragged around the margins just to see what it did. It seemed to do nothing (I still have no idea what it is even supposed to do) and after clicking out of it, my mouse will not click on certain things for about 15-20 seconds. Nothing changed on multiple reboots. After some experimenting it seems like the system is just taking forever to process where the windows are and what is valid to click on. It tends to work fine until a significant change in the window arrangement is made like opening a new window or closing out of a video game. I tried rolling back to previous snapshots. It seemed to work last night, but right before I started typing this today I noticed it doing it again. Sometimes I cant click the task bar, sometimes only a certain window, sometimes no windows, sometimes no windows or the task bar, sometimes the task bar works but I cannot click on anything within the application launcher. Then if I wait for a little while it works fine for a bit. I read that maybe having two monitors is doing it, but it still happened when I disconnected a monitor and rebooted. Is it possible that opening the tiling manager for the first time enabled something that is now causing the system to get tied up and be slow? If so, can I disable the tiling manager in some way?

Fedora 44 KDE, AMD 9070XT, Ryzen 7 9700X, KDE 6.7.4

Any help is appreciated and I’m happy to provide any additional info that would be helpful. I think I’m tech-competent for an amateur, but I have only been using linux for 6-8 months so feel free to assume I am ignorant.

2

@clamjames for a solution you can just answer your selves with a “Blockquote” and then mark the topic as a solution (as I do now).

Btw, welcome to Fedora @clamjames

3

Hello again,

Turns out this was not solved. I cannot for the life of me figure out what causes the bug to happen, but I have found out that it is my corsair Dark Omen mouse. After the above commands were used, it seemed to work fine for about a week, but suddenly started doing it again. I ran the commands again and nothing changed. Since then I actually used my brain a little and tried my old garbage Red Dragon mouse. After several days of using them both and noticing when the bug happens and what fixes it: It happens seemingly randomly while using the corsair and is fixed after disconnecting the corsair and clicking around with the red dragon for a few seconds. I even connected the corsair to my wife’s windows computer to use the iCUE software and check for a firmware update, but it was up to date.

Considering that it persists for a few seconds while using the RD mouse, it doesn’t seem like a hardware issue. Could this be an issue a recent Fedora update? I would be happy to provide logs and whatnot to help with trouble shooting, and don’t hesitate to over-explain to me. I’m not an idiot, but I am absolutely a linux noob.

I would really like to get this fixed as this is a fantastic mouse otherwise, and I’d really prefer to not spend another $60-100 on a mouse I don’t even like as much.

Thanks!