After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 771084 - Cannot enter custom keyboard shortcuts using Super key - 3.21 regression
Cannot enter custom keyboard shortcuts using Super key - 3.21 regression
Status: RESOLVED DUPLICATE of bug 771058
Product: gnome-control-center
Classification: Core
Component: Keyboard
3.21.x
Other Linux
: Normal normal
: ---
Assigned To: Rui Matos
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-09-08 23:07 UTC by Daniel Boles
Modified: 2016-09-08 23:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Daniel Boles 2016-09-08 23:07:24 UTC
Procedure
* Have GNOME Control Centre 3.21.90
* Open Keyboard panel
* Click on a shortcut list row, to open the popup window to customise it
* Try to enter a combo consisting of Super+any other key. For example, try to bind Minimise to Super+Down, like in many other DEs.

Expected results
* The system will accept and use the keyboard shortcut that the user wants.

Actual results
* It does not recognise that a shortcut has been entered
* The popup's close button is inoperable
* I have to press Esc in order to make the close button work

So I can't enter my shortcut in Settings - I have to use dconf-editor.

Such key combinations worked absolutely fine in the previous version of Settings with the old GUI, and are still displayed properly in the new GUI, but they can't be added using it, only dconf.

Hope this helps and thanks in advance. I normally record videos, but obviously that's not much use here. If you need any other info, please let me know.
Comment 1 Bastien Nocera 2016-09-08 23:40:44 UTC
Thanks for taking the time to report this.
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 771058 ***