github-starred/barrier

Fork 0

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

[GH-ISSUE #662] Some keys stop working / swapped functions - on FreeBSD #525

New issue

Closed

opened 2026-05-05 06:35:49 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 06:35:49 -06:00

Owner

Originally created by @Onepamopa on GitHub (May 9, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/662

Operating Systems

Server: Windows 10 x64 1909 18363.815

Client: FreeBSD 12.1-RELEASE-p3 GENERIC

Barrier Version

Server: 232-snapshot-210c2b70
Client: 2.3.2 from the ports tree

Client startup line: barrierc --daemon --display :0 --no-tray --debug INFO --name dev --enable-drag-drop --enable-crypto [SERVER-IP]:24800

Steps to reproduce bug

On the client - Some keys are not working, other have swapped function:
Up/Left/Right arrow keys not working
Down key results in "Return"
Insert - /
Delete - Print screen
Home/End - not working
PrtScr/SysRq - Up
Pause/Break - Home

Other info

When did the problem start to occur? Yesterday
Is there a way to work around it? I haven't found one yet
Does this bug prevent you from using Barrier entirely? > Y E S <

Tested with another client - Kali Linux, barrier 2.3.2 - works fine.
I'll be glad to provide any additional information.

Originally created by @Onepamopa on GitHub (May 9, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/662 ### Operating Systems ### Server: Windows 10 x64 1909 18363.815 Client: FreeBSD 12.1-RELEASE-p3 GENERIC ### Barrier Version ### Server: 232-snapshot-210c2b70 Client: 2.3.2 from the ports tree - Client startup line: barrierc --daemon --display :0 --no-tray --debug INFO --name dev --enable-drag-drop --enable-crypto [SERVER-IP]:24800 ### Steps to reproduce bug ### On the client - Some keys are not working, other have swapped function: Up/Left/Right arrow keys not working Down key results in "Return" Insert - / Delete - Print screen Home/End - not working PrtScr/SysRq - Up Pause/Break - Home ### Other info ### * When did the problem start to occur? Yesterday * Is there a way to work around it? I haven't found one yet * Does this bug prevent you from using Barrier entirely? **> Y E S <** Tested with another client - Kali Linux, barrier 2.3.2 - works fine. I'll be glad to provide any additional information.

gitea-mirror

2026-05-05 06:35:49 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-05 06:35:55 -06:00

Author

Owner

@Onepamopa commented on GitHub (May 23, 2020):

Has anyone actually checked this? It's F****** annoying AF..

@Onepamopa commented on GitHub (May 23, 2020): Has anyone actually checked this? It's F****** annoying AF..

gitea-mirror commented

2026-05-05 06:35:57 -06:00

Author

Owner

@Onepamopa commented on GitHub (Jul 22, 2020):

So far I've figured the following:

If I start the client: barrierc via SDDM /usr/local/share/sddm/scripts/Xsetup - The keys get scrambled.
barrierc --daemon --display :0 --no-xinitthreads --debug INFO --name dev --enable-drag-drop --enable-crypto [ServerIP]:24800

If I start barrier again after user login and kill the previous instance - the keys work normally, however, I can't find a way to run the barrier client in a way that would allow me to login via sddm. Auto-login is out of the question.

Any thoughts, anyone?

@Onepamopa commented on GitHub (Jul 22, 2020): So far I've figured the following: If I start the client: barrierc via SDDM /usr/local/share/sddm/scripts/Xsetup - The keys get scrambled. barrierc --daemon --display :0 --no-xinitthreads --debug INFO --name dev --enable-drag-drop --enable-crypto [ServerIP]:24800 If I start barrier again after user login and kill the previous instance - the keys work normally, however, I can't find a way to run the barrier client in a way that would allow me to login via sddm. Auto-login is out of the question. Any thoughts, anyone?

gitea-mirror commented

2026-05-05 06:36:01 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 22, 2020):

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Sep 22, 2020): This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

gitea-mirror commented

2026-05-05 06:36:04 -06:00

Author

Owner

@p12tic commented on GitHub (Jan 10, 2021):

Let's not close bugs for no reason.

@p12tic commented on GitHub (Jan 10, 2021): Let's not close bugs for no reason.

gitea-mirror commented

2026-05-05 06:36:06 -06:00

Author

Owner

@Onepamopa commented on GitHub (Jan 18, 2021):

Actually this gets fixed by properly configuring the keyboard @ xorg.conf. For some reason during installation the keyboard was not added so I added it manually:

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "us"
Option "XkbModel" "pc105"
EndSection

@Onepamopa commented on GitHub (Jan 18, 2021): Actually this gets fixed by properly configuring the keyboard @ xorg.conf. For some reason during installation the keyboard was not added so I added it manually: Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbLayout" "us" Option "XkbModel" "pc105" EndSection

gitea-mirror referenced this issue

2026-05-05 07:58:36 -06:00

[PR #525] [MERGED] Add autoStart setting #1649