github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #197] F13, F14, F15 not working on Linux client #160

New issue

Closed

opened 2026-05-05 05:27:34 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 05:27:34 -06:00

Owner

Originally created by @maeks84 on GitHub (Dec 12, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/197

Operating Systems

Server: macOS High Sierra 10.13.6

Client: Linux Mint 19 Tara MATE

Barrier Version

2.1.0

Steps to reproduce bug

Try to use the F13, F14, F15 keys.

Other info

When did the problem start to occur? When I tried to use the F13, F14, F15 keys.
Is there a way to work around it? No
Does this bug prevent you from using Barrier entirely? No

Linux client recognizes that a key was pressed. Log after pressing F15 at Debug1.
[2018-12-12T16:48:08] DEBUG1: recv key down id=0x0000efcc, mask=0x0000, button=0x0072
[2018-12-12T16:48:08] DEBUG1: mapKey efcc (61388) with mask 0000, start state: 0000
[2018-12-12T16:48:08] DEBUG1: key efcc is not on keyboard
[2018-12-12T16:48:09] DEBUG1: recv key up id=0x00000000, mask=0x0000, button=0x0072

However, the keys do work when plugging the keyboard in directly.

Originally created by @maeks84 on GitHub (Dec 12, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/197 ### Operating Systems ### Server: macOS High Sierra 10.13.6 Client: Linux Mint 19 Tara MATE ### Barrier Version ### 2.1.0 ### Steps to reproduce bug ### Try to use the F13, F14, F15 keys. ### Other info ### * When did the problem start to occur? When I tried to use the F13, F14, F15 keys. * Is there a way to work around it? No * Does this bug prevent you from using Barrier entirely? No Linux client recognizes that a key was pressed. Log after pressing F15 at Debug1. [2018-12-12T16:48:08] DEBUG1: recv key down id=0x0000efcc, mask=0x0000, button=0x0072 [2018-12-12T16:48:08] DEBUG1: mapKey efcc (61388) with mask 0000, start state: 0000 [2018-12-12T16:48:08] DEBUG1: key efcc is not on keyboard [2018-12-12T16:48:09] DEBUG1: recv key up id=0x00000000, mask=0x0000, button=0x0072 However, the keys do work when plugging the keyboard in directly.

gitea-mirror

2026-05-05 05:27:34 -06:00

closed this issue
added the
macOS

linux
labels

gitea-mirror commented

2026-05-05 05:27:41 -06:00

Author

Owner

@guyzmo commented on GitHub (Nov 4, 2020):

F13 should be keycode 105 on Macos (as returned by karabiner).
I'm using F13 to emulate the compose key locally, and I would like to bind it to the compose key as well on linux :)

I can confirm that F13 to F24 don't work with OSX server, and Linux client.

@guyzmo commented on GitHub (Nov 4, 2020): F13 should be keycode 105 on Macos (as returned by karabiner). I'm using F13 to emulate the compose key locally, and I would like to bind it to the compose key as well on linux :) I can confirm that F13 to F24 don't work with OSX server, and Linux client.

gitea-mirror commented

2026-05-05 05:27:44 -06:00

Author

Owner

@maeks84 commented on GitHub (Aug 22, 2021):

Working on this again. Tried several workarounds, all of which failed. I'm thinking that this is more of a Linux problem. Simply that the Linux install does not think that F13+ are on the keyboard, therefore they are not mapped. I'm trying to figure out how to add these keys to the map, but I'm having no luck yet. Where does Barrier look to find the hex value of the key? Is there a way to modify this file?

Workarounds could be the ability to remap a key to another key or using hotkeys, have an option that it only works on the active computer. As far as I can figure though, these options are not built into Barrier.

@maeks84 commented on GitHub (Aug 22, 2021): Working on this again. Tried several workarounds, all of which failed. I'm thinking that this is more of a Linux problem. Simply that the Linux install does not think that F13+ are on the keyboard, therefore they are not mapped. I'm trying to figure out how to add these keys to the map, but I'm having no luck yet. Where does Barrier look to find the hex value of the key? Is there a way to modify this file? Workarounds could be the ability to remap a key to another key or using hotkeys, have an option that it only works on the active computer. As far as I can figure though, these options are not built into Barrier.

gitea-mirror commented

2026-05-05 05:27:49 -06:00

Author

Owner

@maeks84 commented on GitHub (Aug 22, 2021):

Hey, I think I got it!

http://xahlee.info/linux/linux_xmodmap_tutorial.html

Create a backup of your original
xmodmap -pke > ~/xmodmap_original

Create a copy of that and edit it to register the F keys
keycode 191 = F13 F13 F13 keycode 192 = F14 F14 F14 keycode 193 = F15 F15 F15

Rename the new file to
~/.Xmodmap

Test with
xmodmap ~/.Xmodmap

Changes did not last through a reboot for me and the _ ~/.xinitrc_ did not work for me.
So I turned into a script and saved it as xmodmap.sh
if [ -s ~/.Xmodmap ]; then xmodmap ~/.Xmodmap fi

I then set this to run at startup after a 3 second delay.

I'll mark this as closed now, especially since the fix was more on the Linux side.

@maeks84 commented on GitHub (Aug 22, 2021): Hey, I think I got it! [http://xahlee.info/linux/linux_xmodmap_tutorial.html](http://xahlee.info/linux/linux_xmodmap_tutorial.html) Create a backup of your original `xmodmap -pke > ~/xmodmap_original` Create a copy of that and edit it to register the F keys `keycode 191 = F13 F13 F13 keycode 192 = F14 F14 F14 keycode 193 = F15 F15 F15` Rename the new file to `~/.Xmodmap` Test with `xmodmap ~/.Xmodmap` Changes did not last through a reboot for me and the _ ~/.xinitrc_ did not work for me. So I turned into a script and saved it as _xmodmap.sh_ `if [ -s ~/.Xmodmap ]; then xmodmap ~/.Xmodmap fi` I then set this to run at startup after a 3 second delay. I'll mark this as closed now, especially since the fix was more on the Linux side.

No labels

Rows
Columns