github-starred/barrier

Fork 0

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

[GH-ISSUE #1029] unable to use capslock as modifier #814

New issue

Open

opened 2026-05-05 07:10:43 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 07:10:43 -06:00

Owner

Originally created by @a-singer on GitHub (Jan 19, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1029

Describe the bug
Hello,

I'm having a bit of an issue using Barrier from windows system to windows system, both running Windows 7. I am totally blind and use the NVDA screen reader

http://www.nvda-project.org
to run my machine. The screen reader uses the capslock key as a modifier. Barrier, however, seems to pass this key through to clients only as a single press, not as a modifier. That is, if I want to hold the capslock key down and hit a, what the client sees is a press and release of the capslock key, then the letter a. It does not see capslock+a. Is there a way to have capslock used as a modifier? I note that there may be a connection with issue #366, but that seems to be on Linux, rather than with Windows at both ends.

To Reproduce

Steps to reproduce the behavior:

Start controling a client.
press and hold the capslock key, then press and release a, and release the capslock key.
Your client should receive capslock+a, but it actually receives capslock down, capslock up, then a down, and a up.

Expected behavior
I expected the client to receive capslock down, then a down, then a up, then capslock up.

Screenshots
If applicable, add screenshots to help explain your problem.

Please do not link to image hosting sites, as these can be ephemeral. Instead, attach them to the issue.

Desktop (please complete the following information):

OS: Windows 7 SP1
Barrier version 2.3.3

Additional context

Add any other context about the problem here.

Originally created by @a-singer on GitHub (Jan 19, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1029 **Describe the bug** Hello, I'm having a bit of an issue using Barrier from windows system to windows system, both running Windows 7. I am totally blind and use the NVDA screen reader http://www.nvda-project.org to run my machine. The screen reader uses the capslock key as a modifier. Barrier, however, seems to pass this key through to clients only as a single press, not as a modifier. That is, if I want to hold the capslock key down and hit a, what the client sees is a press and release of the capslock key, then the letter a. It does not see capslock+a. Is there a way to have capslock used as a modifier? I note that there may be a connection with issue #366, but that seems to be on Linux, rather than with Windows at both ends. **To Reproduce** Steps to reproduce the behavior: 1. Start controling a client. 2. press and hold the capslock key, then press and release a, and release the capslock key. 3. Your client should receive capslock+a, but it actually receives capslock down, capslock up, then a down, and a up. **Expected behavior** I expected the client to receive capslock down, then a down, then a up, then capslock up. **Screenshots** If applicable, add screenshots to help explain your problem. Please do not link to image hosting sites, as these can be ephemeral. Instead, attach them to the issue. **Desktop (please complete the following information):** - OS: Windows 7 SP1 - Barrier version 2.3.3 **Additional context** Add any other context about the problem here.

gitea-mirror commented

2026-05-05 07:10:45 -06:00

Author

Owner

@clort81 commented on GitHub (Sep 5, 2023):

I have been using Xmodmap to modify capslock on a linux client, and this consistently breaks keyboard with barrier running.
Symptoms seem to include losing some keys (capital keys), getting ctrl-key stuck (every click or keypress is interpreted as ctrl-click - etc).

At the time of this writing, I simply have to not use a redirected capslock, and Barrier sharing works finel.

Thanks to the poster for pointing me to this issue.

@clort81 commented on GitHub (Sep 5, 2023): I have been using Xmodmap to modify capslock on a linux client, and this consistently breaks keyboard with barrier running. Symptoms seem to include losing some keys (capital keys), getting ctrl-key stuck (every click or keypress is interpreted as ctrl-click - etc). At the time of this writing, I simply have to not use a redirected capslock, and Barrier sharing works finel. Thanks to the poster for pointing me to this issue.

No labels

Rows
Columns