GNOME Bugzilla – Bug 670579
Generate warning when action is hard-coded too
Last modified: 2021-06-09 16:33:26 UTC
Steps to reproduce: 1. Launch gnome-control-center 2. Go to Keyboard - Shortcuts - Custom shortcuts 3. Add any command and set XF86ScreenSaver as shortcut button 4. Press XF86ScreenSaver Expected result: Custom command being run. Actual result: Custom command runs and the session is being locked.
The button's use is hardcoded: http://git.gnome.org/browse/gnome-settings-daemon/tree/plugins/media-keys/shortcuts-list.h#n108 And we don't have support in gnome-control-center for detecting those hard-coded actions. We should warn when the user tries to override them.
This seems to be a duplicate of https://bugzilla.gnome.org/show_bug.cgi?id=660566
*** Bug 690154 has been marked as a duplicate of this bug. ***
From bug 690154: The sleep button on the keyboard (XF86Sleep -- keycode 150) cannot be reassigned by the gnome-control-center GUI. This is because the power buttons on the computer (including those on the keyboard) are controlled by the following dconf settings: org.gnome.settings-daemon.plugins.power button-hibernate org.gnome.settings-daemon.plugins.power button-power org.gnome.settings-daemon.plugins.power button-sleep org.gnome.settings-daemon.plugins.power button-suspend The gnome-control-center GUI doesn't know about or manage these settings. The keyboard sleep button is annoyingly easy to press by mistake, making the computer suddenly sleep without any warning. I can re-assign the button using the gnome-control-center GUI after I use dconf-editor to set button-hibernate, button-sleep, and button-suspend to 'nothing'. My preference would be for the sleep button (on the keyboard) to be able to be re-assigned (rather than a warning message saying that it can't).
(In reply to comment #4) > From bug 690154: <snip> > My preference would be for the sleep button (on the keyboard) to be able to be > re-assigned (rather than a warning message saying that it can't). I've said in the other bug that this wouldn't happen. Please keep this bug on topic.
This bug's title is not very descriptive. Can somebody who can edit it please change it to: Keyboard buttons with special purpose should not be assignable via Gnome Control Center GUI -- generate a warning dialog
*** Bug 732282 has been marked as a duplicate of this bug. ***
*** Bug 707894 has been marked as a duplicate of this bug. ***
*** Bug 689236 has been marked as a duplicate of this bug. ***
*** Bug 771124 has been marked as a duplicate of this bug. ***
Created attachment 335205 [details] [review] keyboard: Build scaffolding for hard-coded shortcut conflicts
Created attachment 335206 [details] [review] keyboard: Error when new shortcut conflicts with system shortcut FIXME the label doesn't disappear, and this doesn't work in the custom shortcut dialogue.
*** Bug 681969 has been marked as a duplicate of this bug. ***
These patches are not applying on master.
Created attachment 367631 [details] [review] keyboard: Build scaffolding for hard-coded shortcut conflicts
Created attachment 367632 [details] [review] keyboard: Error when new shortcut conflicts with system shortcut FIXME the label doesn't disappear, and this doesn't work in the custom shortcut dialogue.
Created attachment 367652 [details] [review] keyboard: Error when new shortcut conflicts with system shortcut FIXME the label doesn't disappear, and this doesn't work in the custom shortcut dialogue.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new bug report at https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/ Thank you for your understanding and your help.