Although this has been answered I'd like to add how I fixed this issue since setxkbmap did not do the trick for me.
For me these 12 commands did it.
These keybindings were set to ['F1'] ~ ['F12'] and what I did was I just set them to empty array.
gsettings set org.gnome.mutter.wayland.keybindings switch-to-session 1 "[]"
gsettings set org.gnome.mutter.wayland.keybindings switch-to-session 2 "[]"
gsettings set org.gnome.mutter.wayland.keybindings switch-to-session 3 "[]"
gsettings set org.gnome.mutter.wayland.keybindings switch-to-session 4 "[]"
gsettings set org.gnome.mutter.wayland.keybindings switch-to-session 5 "[]"
gsettings set org.gnome.mutter.wayland.keybindings switch-to-session 6 "[]"
gsettings set org.gnome.mutter.wayland.keybindings switch-to-session 7 "[]"
gsettings set org.gnome.mutter.wayland.keybindings switch-to-session 8 "[]"
gsettings set org.gnome.mutter.wayland.keybindings switch-to-session 9 "[]"
gsettings set org.gnome.mutter.wayland.keybindings switch-to-session 10 "[]"
gsettings set org.gnome.mutter.wayland.keybindings switch-to-session 11 "[]"
gsettings set org.gnome.mutter.wayland.keybindings switch-to-session 12 "[]"
Obviously this fix only applies to people who use Gnone + Mutter + Wayland (I use Redhat linux)
How I found this fix:
gsettings list-recursively | grep F10
To find out all the keybindings that includes F10 and then among many results, I saw
org.gnome.mutter.wayland.keybindings switch-to-session-10 ['<Primary><Alt>F10']
So I figured that keybinding must be it, and ran
gsettings list-keys org.gnome.mutter.wayland.keybindings to find out all the similar keybinds
Lastly, I thank this thread and especially the user who commented Super+F2 recovers the computer back to GUI from the black screen. Saved countless rebooting for me