setting custom keyboard shortcut fails for certain keys

Bug #1851134 reported by Christopher Barrington-Leigh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

I click on settings in menu or press my settings icon key (above F9 key on Lenovo T450s keyboard). Navigate to "Keyboard Shortcuts". Scroll to bottom to press "+" to add a custom shortcut. Define function, then click on "Set Shortcut...". Then I press the "Explorer" key, which is above the F12 on my keyboard. Instead of setting the shortcut, it brings up a file browser.
I can set my shortcut to shift-Explorer, but not to Explorer. This is even though no other keyboard shortcut listed is set to this key "Explorer". The "Home folder" Launcher is set to "Disabled".
Changing the "Home folder" launcher keyboard shortcut to something else does not help.

Instead, once I click on "set Shortcut", it should listen to whatever I choose.

The same problem exists for the "Search" key.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-settings-daemon 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 3 09:29:28 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-01-24 (282 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to eoan on 2019-10-31 (2 days ago)

Revision history for this message
Christopher Barrington-Leigh (cpbl) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, could you report the issue upstream on
https://gitlab.gnome.org/GNOME/gnome-control-center/issues

affects: gnome-settings-daemon (Ubuntu) → gnome-control-center (Ubuntu)
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Christopher Barrington-Leigh (cpbl) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.