Cursor keeps moving when changing workspace

Hello,

I am having some troubles since I updated to Fedora 43. Whenever I change workspace, the cursor keeps moving to the left in the window getting focus in this new workspace.

This is very annoying and is appearing every window, not one specific program.

I have disconnected my bluetooth keyboard and the issue is still present. I have upgraded / rebooted my system but it still isn’t fixed.

Any idea of something I could try to fix it?

Thank you very much and have a good day.

Precision: If I use super+1 or super+2 it changes workspace but keeps pressing 2 or 1.

Which desktop are you on? Gnome? KDE?

Oh, yes I am sorry, I should have mentioned it. I am on Gnome!

1 Like

I haven’t seen this behavior on F43 reported here yet. How are you switching workspaces: mouse, trackpad, keyboard?

Do you have any GNOME extensions installed? If so, you could try to reproduce with extensions disabled. Another test would be with a newly created user.

I disabled all extensions and it’s still doing the weird behavior.

Will try the new user, thanks for the idea!

I am switching via keyboard! Either via cmd+1 or ctrl-alt-left.

OK, I curious of the outcome when tested with a new user.

I had the same problem, i have already reported it on Gnome GitLab: Gnome GitLab Issue

3 Likes

Thank you for your answer! Yes, that seems to be it. Glad to know I’m not the only one and that it’s been properly reported.

Have a good day.

Downgrade mutter

sudo dnf downgrade mutter-49.1-1.fc43

Thanks for that.

[edit] Unfortunately, downgrading mutter causes the GNOME session to crash when dragging video files. That’s actually a worse issue than the hotkey getting stuck until I press another key.

I’ve been struggling with this for a bit while running vscode and after some digging, it looks like a problem with vscode and possibly other electron apps running on xwayland. I haev posted the solution below for the vscode app but it should work on all electron apps you might be facing the issue with.

Setting vscode to run native wayland fixed this issue for me. The exact solution will depend on how vsc is installed and run on your system, but it involves passing this flag when you try to run it: --ozone-platform-hint=wayland

In my case, I created an override to the command that runs code from my desktop navbar.

Exec=/usr/share/code/code --ozone-platform-hint=wayland --enable-features=WaylandWindowDecorations %F

you can try this on terminal first with:
code --ozone-platform-hint=wayland

you might get a warning that code does not recognize this, but thats ok, electron will pick this up. try moving workspaces, if it works, figure out how to do the permanent fix.

hope this helps