Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#45936 - [gnome-control-center] Microsoft Sculpt Ergonomic Keyboard: not all media keys work

Attached to Project: Arch Linux
Opened by Lucas (tr4ce) - Sunday, 09 August 2015, 16:47 GMT
Last edited by Toolybird (Toolybird) - Monday, 29 May 2023, 00:41 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



I have a Microsoft Sculpt Ergonomic Keyboard [1]. It has a row with combined F1..F12 keys and media keys. Using a hardware switch you can decide which functionality you want to use. Unfortunately, I cannot get the media keys to work.

When I open the GNOME System preferences -> Keyboard -> Shortcuts, and I try to set the play/pause, mute, volume down, volume up keys, the GNOME preferences window does not recognize a key press. To illustrate further:

1. You have the shortcuts window open
2. You want to register a new keybinding for play/pause
3. You click on the play/pause row, and it says "New accelerator.."
4. You push the play/pause button on your keyboard
5. Nothing happens. No key is detected and the window still says "New accelerator.."

Some extra strangeness: the search button on my keyboard is recognized as Shift+Super+Touchpad Toggle

Using showkey --scancodes I find the following scancodes:

0xe0 0x22
0xe0 0xa2

0xe0 0x20
0xe0 0xa0

Volume down:
0xe0 0x2e
0xe0 0xae

Volume up:
0xe0 0x30
0xe0 0xb0

0xaa 0xe0 0xdb 0xf4
0x2a 0xe0 0x5b 0x74

F6 media key (I don't know what the icon means):
0x38 0xe0 0x5b 0x74
0xb8 0xe0 0xdb 0xf4

F7 media key (I don't know what the icon means):
0x1d 0xe0 0x5b 0x74
0x9d 0xe0 0xdb 0xf4

0xe0 0x5b 0x74
0xe0 0xdb 0xf4

F9 media key (I don't know what the icon means):
0x1d 0xe0 0x5b 0x0e
0x9d 0xe0 0xdb 0x8e

F10 media key (I don't know what the icon means):
0x1d 0xe0 0x5b 0x0f
0x9d 0xe0 0xdb 0x8f

(It always inserts some tab before the scan code)

F11 media key (Tile window left?):
0x38 0xe0 0x5b 0xe0 0x79
0xb8 0xe0 0xdb 0xe0 0xf9

F12 media key (Tile window bottom?):
0x1d 0xe0 0x5b 0x6d
0x9d 0xe0 0xdb 0xed

0xe0 0x21
0xe0 0xa1

This image gives a nice overview of the media key icons:

To conclude: no media key performs the expected action. Most of them do nothing, and the search tool also triggers a "super" button press.

What would I need to do to fix this? If you would like to see any configuration file, please let me know.

I'm running on up to date Arch Linux with GNOME.

This task depends upon

Closed by  Toolybird (Toolybird)
Monday, 29 May 2023, 00:41 GMT
Reason for closing:  No response
Additional comments about closing:  Plus it's old and stale. If still an issue, please report upstream.
Comment by Doug Newgard (Scimmia) - Monday, 10 August 2015, 15:51 GMT
  • Field changed: Summary (Microsoft Sculpt Ergonomic Keyboard: not all media keys work → [gnome-control-center] Microsoft Sculpt Ergonomic Keyboard: not all media keys work)
  • Field changed: Status (Unconfirmed → Assigned)
  • Task assigned to Jan Alexander Steffens (heftig), Jan de Groot (JGC)
Taking a guess at where the problem could be.
Comment by Jeffery MacEachern (jaem) - Friday, 02 October 2015, 11:33 GMT
I can confirm the exact situation and output of showkeys as OP, with the exception that I believe the output for Search/(F5 media key) was a typo and should be in the opposite order.
0xaa 0xe0 0xdb 0xf4
0x2a 0xe0 0x5b 0x74

However if it helps narrow things down I can confirm that the expected behaviour has been present for me under Fedora 22 for months; I'm not sure which package is the problem, but I can compare versions/distro patches between that install and Arch if you'd like.

Edit: addendum, this is definitely not specific to GNOME.
Comment by mattia (nTia89) - Thursday, 10 March 2022, 17:14 GMT
Do you still suffer of this issue?