GNOME Bugzilla – Bug 161762
don't allow to set keybindings that are used by the window manager or g-s-d
Last modified: 2021-06-10 16:04:17 UTC
- Invoke gnome-terminal - Click on 'Edit->Keyboard Shortcuts' - Select File->New Profile' - Set shortcut key to '<Shift><Ctrl><Alt><Escape> - Click on 'Close' - Press SHIFT+CTRL+ALT+ESC The 'new profile' dialog does not open.
<Ctrl><Alt><Esc> key binding is already associated with Moving between windows and panel. I believe thatz why it is not working with new profile. I tried with other shortcut keys for gnome-terminal, new profile and they work fine.
I've changed the keybinding of 'Moving between windows and panel' to CTRL+ALT+SPACE. Still the problem persists. Also, gnome-keybindings shows that CTRL+ALT+ESC is the combination for focussing on windows/Desktop. But for the terminal we are using the Shift modifier. I wonder why shift is not being recognised.
I believe alt+space also is bound to the window manager as well, so that would also probably be impossible for the terminal to recognize. Not sure, though. Does it work with, say, ctl+alt+b?
I tried with ctrl+alt+b and other key combinations which are not already tied to the window manager and the keyboard shortcut works fine with those.
Looks to me like shift is indeed ignored here, move focus between panels etc is bound to ctrl+alt+esc, but it also does that with the shift modifier. Is this a more general keyboard/window manager related bug?
Think so (shift means tab in the opposite direction), cc'ing metacity-maint
Yes, shift means going in the opposite direction, and replacing tab with esc means cycle immediately (and without the popup). Both can be applied in any combination to either alt-tab (cycling through normal windows) or ctrl-alt-tab (cycling through special windows). I would think that gnome-terminal could detect WM keybindings and avoid letting the user choose them. Raj: What do you mean by the 'Moving between windows and panel' keybinding in comment 2?
Retitling to make it clear what should be done here (see comment 7).
Thanks for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. This bug report should be set to OBSOLETE.
Closing as OBSOLETE as per last comment. Please reopen if you think this is inapproproate.
chpe@gnome.org why did you change the resolution to unconfirmed? I would like to know please?
(In reply to comment #11) > chpe@gnome.org why did you change the resolution to unconfirmed? I would like > to know please? Because he thinks that the bug is still relevant. He's the maintainer.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/3009.