F13-F16 function keys not registering correctly for shortcuts in calc

I want to assign some macros (they work as expected) to the F13-F16 shortcut keys.

I’m on LibreOffice 24.8.6.2 480(Build:2). Arch Linux with kernel 6.13.8-arch1-1. Running X, not wayland.

When I go to Tools → Customize → Keyboard and click in the Shortcut Keys area and then type F13-F16 this is what I get:

F13 → Does not register at all
F14 → Maps to the Undo shortcut
F15 → Works correctly, maps to F15
F16 → Maps to the Copy shortcut

I’ve checked the keys are sending the correct keycodes via xev.

I can assign macros to F15 fine as it works as intended. I can assign macros that work when I hit F14 and F16, but I have to map them to the Undo/Copy shortcuts. F13 I can’t get to do anything.

This feels like it might be a bug, but maybe I’m missing something. Has anyone else experienced this that could point me in the right direction?

“Regular” keyboards these days have 12 numbered F-keys. While LO supports up to F-16, the last four are “exceptions” not always found so I guess not many apps make use of them. To make them useful, it may well be that they are programmable, either in HW or in an installable driver. There may also be a keyboard shortcut to switch between “plain” F13 - F16 keying and “programmed mode”. Look for a tiny padlock symbol with an F inside.

Assuming HW programming, it appears that your keyboard has been programmed to send ctrl-Z from F-14 and Ctrl-C from F-16. (With customising by driver “anything is possible”, but that would probably require some conscious setup by you.)

I missed the line

Then “customised by driver” is possible, either globally or a dedicated setup for specific apps. Check in documentation whether your particular keyboard (or computer, if the keyboard is integrated; typically laptops) offers F-key customisation by any means.

It is a Keychron keyboard. It runs QMK. I have set F13-F24 on a second layer. Other than programming the layers and swapping Esc/Caps I haven’t made any kind of other customizations to the QMK firmware.

For what it’s worth, they (F13+) work in Krita.

Have to look for a solution elsewhere then. I don’t have access to that keyboard, nor do I have a workstation with an environment similar to yours at the moment, so the only suggestions I can provide are the general suggestions I have already given. Sorry!

Someone else may know more. Wait for it!
It is also possible that there is a bug causing your issue.

I appreciate your suggestions. Thank you for taking the time to chime in. Have a good day.