GNOME Bugzilla – Bug 772506
ctrl+backspace doesn't work in core gnome apps under wayland if ctrl+alt+backspace combo is enabled
Last modified: 2018-04-23 17:23:30 UTC
Ctrl+Backspace is used to erase the last word. It works everywhere under X11. Under Wayland, though, it doesn't work in any core gnome apps. These apps were tested: gedit nautilus (rename/new dir dialog) gnome-clocks (add new city dialog) gnome-maps (search) gnome-software (search) gnome-weather (search) gnome-characters (search) totem (add url) But it still works here (even under Wayland): alt+f2 "run command" firefox hexchat So this doesn't seem to be an universal gtk bug. Therefore reporting against compositor, but honestly I don't really know where to place this. firefox-49.0-2.fc25.x86_64 gedit-3.22.0-2.fc25.x86_64 gnome-characters-3.22.0-1.fc25.x86_64 gnome-clocks-3.22.0-2.fc25.x86_64 gnome-maps-3.22.0-1.fc25.x86_64 gnome-shell-3.22.0-1.fc25.x86_64 gnome-software-3.22.0-1.fc25.x86_64 gnome-terminal-nautilus-3.22.0-1.fc25.x86_64 gnome-weather-3.20.2-1.fc25.noarch gtk2-2.24.31-2.fc25.x86_64 gtk3-3.22.0-2.fc25.x86_64 hexchat-2.12.1-4.fc25.x86_64 mutter-3.22.0-2.fc25.x86_64 nautilus-3.22.0-1.fc25.x86_64 totem-3.22.0-1.fc25.x86_64
Works fine in gedit, gnome-clocks, gnome-software, etc. Basically in any app I tried it worked here.
It works for my colleague as well, and when I created a fresh new user account, it also works. So this seems to be a configuration issue. In my main user account, I tried disabling all shell extensions, disabling all startup apps, uninstalling all testing updates, and it's still broken. Any idea how to debug why it is broken (and only in certain apps)?
Found it. If I enable Ctrl+Alt+Backspace combo in gnome-tweak-tool, Ctrl+Backspace breaks in gedit etc.
Confirmed on Arch Linux, mutter 3.26.2+31+gbf91e2b4c-1
-> duplicate of bug #754110
Thanks, marking as such. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 754110 ***