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 689236 - XF86ScreenSaver, Delete, Print Screen, Scroll Lock and Media player keys cannot be assigned to a keyboard shortcut
XF86ScreenSaver, Delete, Print Screen, Scroll Lock and Media player keys cann...
Status: RESOLVED DUPLICATE of bug 670579
Product: gnome-control-center
Classification: Core
Component: Keyboard
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
3.10
Depends on:
Blocks:
 
 
Reported: 2012-11-28 18:23 UTC by Tomáš Hnyk
Modified: 2016-09-08 15:52 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tomáš Hnyk 2012-11-28 18:23:09 UTC
Opening a new bug as instructed here in bug 660566 .

To reproduce
1. Launch gnome-control-center
2. Go to Keyboard - Shortcuts - Custom shortcuts
3. Assign any of the keys in set [XF86ScreenSaver, Delete, Scroll Lock and Media player keys]
4. Press the keys

Expected result:
Sound is muted.

Actual result:
Depending on the key, nothing happens or another action associated with the key is run.

Also note that System Settings ▸ Keyboard ▸ Shortcuts ▸ Launchers ▸ Launch
Terminal works with all these keys, so only some actions cannot be assigned to
these keys. Also, it seems that key combinations such as Alt+Menu work for all
actions. From the linked bug report, Jasper St. Pierre says "Keybindings handled inside the compositor (mutter) will work, but others
instead handled by gnome-settings-daemon or a third-party program will not. We
will be removing this distinction for 3.8."

I am not sure whether it will solve the issue (I guess not).

As the reasoning from bug 685286 by Bastien Nocera is "[if] it's not a modifier, it should work", I am not requesting that these keys necessarily can be assigned to any command (although I do not think that they are modifiers). But if they are not allowed to be assigned, gnome-control-centre should tell the user that she is trying to do something impossible and not accept the keys as now and then silently fail. Also not that the list of the keys that are affected by this may not be complete.
Comment 1 Bastien Nocera 2016-09-08 15:52:19 UTC
The problem is that some of those keys are already assigned to hard-coded functions.

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 670579 ***