[GH-ISSUE #1058] Keypress hotkey does not trigger on the server screen #841

Open
opened 2026-05-05 07:12:41 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @Azzurite on GitHub (Feb 8, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1058

Describe the bug

If you create a "key press" hotkey, for example when 1 is pressed, then press 2, and select the server screen as "Only on these screens", I would expect that when I press 1, that the server screen receives a 2. However, this only seems to work on client screens.

To Reproduce

Steps to reproduce the behavior:

  1. Go to 'Server Configuration' -> Hotkeys
  2. Create a new hotkey with key 1
  3. Add an action to this hotkey
    • Select 'Press and release a hotkey`
    • Set the keystroke to 2
  4. Switch on 'Only on these screens`
  5. Select the server screen
  6. Restart barrier
  7. Press 1
  8. No 2 is pressed on the selected screen

Expected behavior

I would expect that when I press 1, the hotkey triggers and sends the keypress 2 to the server screen.

I would also expect that when I create a hotkey 1 that then also presses 1, that that also works on the server screen, i.e. the hotkey is visible to the OS instead of getting blocked.

Desktop (please complete the following information):

  • OS: Windows 10
  • Barrier version 2.3.3-release-3395cca9
Originally created by @Azzurite on GitHub (Feb 8, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1058 **Describe the bug** If you create a "key press" hotkey, for example when `1` is pressed, then press `2`, **and** select the server screen as "Only on these screens", I would expect that when I press `1`, that the server screen receives a `2`. However, this only seems to work on client screens. **To Reproduce** Steps to reproduce the behavior: 1. Go to 'Server Configuration' -> Hotkeys 1. Create a new hotkey with key `1` 1. Add an action to this hotkey * Select 'Press and release a hotkey` * Set the keystroke to `2` 1. Switch on 'Only on these screens` 1. Select the server screen 1. Restart barrier 1. Press `1` 1. No `2` is pressed on the selected screen **Expected behavior** I would expect that when I press `1`, the hotkey triggers and sends the keypress `2` to the server screen. I would also expect that when I create a hotkey `1` that then also presses `1`, that that also works on the server screen, i.e. the hotkey is visible to the OS instead of getting blocked. **Desktop (please complete the following information):** - OS: Windows 10 - Barrier version 2.3.3-release-3395cca9
Author
Owner

@sblatnick commented on GitHub (Mar 8, 2021):

I think I am seeing the same behavior.

Server: 2.3.3-release-12024b9a on Debian, built myself from the master branch to get Sun keyboard support.
Client: 2.3.3-release-6f45a8ac on MacOS Catalina

I set up a hotkey to map the Sun keyboard's Help key to press F1, and it only sends the keypress to the client machine, not the server.

I would expect the button to be pressed on both boxes, but I also wouldn't mind if the keypress were dependent on the machine with the focus. Alternatively, if I could get the Sun keys to be passed to MacOS without using hotkeys at all, I could accomplish the same thing using karabiner.

The situation this presents is either I can use the Help key on my server/linux box natively (no hotkey defined), or I can use it on my client/mac, but there is no way I know of to have the key work on both boxes. In other words, if I specify the hotkey, neither Help nor F1 keypress invokes the desired UI interaction in Compiz Fusion running on the server/debian box. However, if I open Compiz Config, and grab a keypress, it will assign the Help key as a shortcut/keybinding.

I've tried various settings of "only on these screens" to no avail. Does this setting mean to trigger the hotkey only when that screen is focused, or only to send the hotkey to those screens? It seems to be the latter.

How are hotkeys supposed to work? Send the key to all applicable screens, or just the focused one? Could we add an option if there isn't one to determine which of these behaviors to use?

<!-- gh-comment-id:792992052 --> @sblatnick commented on GitHub (Mar 8, 2021): I think I am seeing the same behavior. Server: 2.3.3-release-12024b9a on Debian, built myself from the master branch to get Sun keyboard support. Client: 2.3.3-release-6f45a8ac on MacOS Catalina I set up a hotkey to map the Sun keyboard's Help key to press F1, and it only sends the keypress to the client machine, not the server. I would expect the button to be pressed on both boxes, but I also wouldn't mind if the keypress were dependent on the machine with the focus. Alternatively, if I could get the Sun keys to be passed to MacOS without using hotkeys at all, I could accomplish the same thing using karabiner. The situation this presents is either I can use the Help key on my server/linux box natively (no hotkey defined), or I can use it on my client/mac, but there is no way I know of to have the key work on both boxes. In other words, if I specify the hotkey, neither Help nor F1 keypress invokes the desired UI interaction in Compiz Fusion running on the server/debian box. However, if I open Compiz Config, and grab a keypress, it will assign the Help key as a shortcut/keybinding. I've tried various settings of "only on these screens" to no avail. Does this setting mean to trigger the hotkey only when that screen is focused, or only to send the hotkey to those screens? It seems to be the latter. How are hotkeys supposed to work? Send the key to all applicable screens, or just the focused one? Could we add an option if there isn't one to determine which of these behaviors to use?
Author
Owner

@PseudoResonance commented on GitHub (Feb 26, 2022):

I've run into this as well. My hotkeys will only send to the client, but it breaks hotkeys on the server. Both of which are running Windows 11 21H2. It doesn't seem to be OS related.

<!-- gh-comment-id:1051572867 --> @PseudoResonance commented on GitHub (Feb 26, 2022): I've run into this as well. My hotkeys will only send to the client, but it breaks hotkeys on the server. Both of which are running Windows 11 21H2. It doesn't seem to be OS related.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#841
No description provided.