after update to fedora 43, a new behavior appears, when I switch between workspaces, the arrow right or left has been pressed infinite.
anyone know how to fix this issue ?
Yeah I’m seeing the same thing. The easiest way for me to replicate it is to open up Visual Studio Code then switch to the next workspace with [CTRL]-[ALT]-[RIGHT ARROW] then [CTRL]-[ALT]-[LEFT ARROW]. Once that is done the cursor will continue moving left in vscode until any other key is pressed. Not sure where to report this though, is it a GNOME, Wayland, Fedora or VS Code bug?
Where is it occurring for you?
Ah it looks like it might be a mutter bug, follow along here: Making sure you're not a bot!
3 Likes
same here,to a few apps (rpm,flatpak)
Apologies for the delay, it is happening on kitty (terminal) and vscode
@smarthall thanks for this links, contain a solution inside of it.
just run: sudo dnf downgrade mutter and wait for mutter update fix.
1 Like
Many thanks for the workaround!
Once you have downgraded mutter you should also sudo dnf versionlock add mutter mutter-common. This will let you continue to upgrade your system while locking those packages in place. Then when a fix is available you can sudo dnf versionlock delete mutter mutter-common and continue updating your system as normal.
3 Likes
thanks buddy 
Thanks Daniel for the excellent tip!
I just find out in man dnf-versionlock that you can even exclude a package, so that when a new version of mutter will come out it will be installed, with:
$ sudo dnf versionlock exclude mutter-49.1.1-1.fc43
With this command dnf upgrade will tell, among the other things:
Skipping packages with conflicts:
mutter-common noarch 49.1.1-1.fc43 updates 36.5 KiB
I hope this is the best and easiest thing to do to hopefully forget about this problem if will be fixed in the next version 
2 Likes
Nice, that’s a much better approach!
Sadly gnome-software doesn’t respect dnf versionlock, be aware.
1 Like
I’ve been struggling with this for a bit and after some digging, it looks like a problem with vscode running on xwayland. 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
1 Like