github-starred/barrier

Fork 0

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

[GH-ISSUE #1646] Keyboard/mouse becomes unresponsive on both host and client #1215

New issue

Open

opened 2026-05-05 07:36:57 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

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

Owner

Originally created by @Vigrond on GitHub (Apr 15, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1646

What happened?

Sometimes, after barrierc is running for a long time (8+ hours), both my Windows 10 host and Ubuntu 21.10 client lose any keyboard/mouse control.

When trying to use the mouse, the cursor graphic on the client will seem to "vibrate" / shake in place rapidly, but is unresponsive.

The cursor graphic on Windows host is non-existent.

When trying to type, neither the host or client receives normal input.

When hitting the windows key, nothing happens.

When hitting ctrl+alt+del, the Windows screen comes up, however as soon as you select "task manager" and the blue screen goes away, the behavior resumes and control over the task manager program is impossible.

Stopping and restarting the client barrier does nothing, and it is unable to reconnect. (Connection rejected)

The only solution seems to be to "Sign Out" from the ctrl alt del menu, or replug in the mouse and keyboard physically.

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

No response

What OSes are you seeing the problem on? (Check all that apply)

Linux, Windows

What OS versions are you using?

Windows 10 Enterprise host
version 10.0.19044 Build 19044

Ubuntu 21.10 client

Relevant log output

No response

Any other information

I will try to update the log next time it happens, since the log seems to be erased every start, I needed to enable the log to file option.

Originally created by @Vigrond on GitHub (Apr 15, 2022). Original GitHub issue: https://github.com/debauchee/barrier/issues/1646 ### What happened? Sometimes, after barrierc is running for a long time (8+ hours), both my Windows 10 host and Ubuntu 21.10 client lose any keyboard/mouse control. When trying to use the mouse, the cursor graphic on the client will seem to "vibrate" / shake in place rapidly, but is unresponsive. The cursor graphic on Windows host is non-existent. When trying to type, neither the host or client receives normal input. When hitting the windows key, nothing happens. When hitting ctrl+alt+del, the Windows screen comes up, however as soon as you select "task manager" and the blue screen goes away, the behavior resumes and control over the task manager program is impossible. Stopping and restarting the client barrier does nothing, and it is unable to reconnect. (Connection rejected) The only solution seems to be to "Sign Out" from the ctrl alt del menu, or replug in the mouse and keyboard physically. ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? _No response_ ### What OSes are you seeing the problem on? (Check all that apply) Linux, Windows ### What OS versions are you using? Windows 10 Enterprise host version 10.0.19044 Build 19044 Ubuntu 21.10 client ### Relevant log output _No response_ ### Any other information I will try to update the log next time it happens, since the log seems to be erased every start, I needed to enable the log to file option.

gitea-mirror commented

2026-05-05 07:37:00 -06:00

Author

Owner

@Vigrond commented on GitHub (Apr 26, 2022):

update...

it seems Ubuntu keeps starting new barrierc processes over time. I found 3 concurrent barrierc processes with the no tray option. In the windows log they were all competing as they were the same client name.

So most of the log looks like this:

started server (IPv4/IPv6), waiting for clients


server status: active
[2022-04-25T19:25:13] INFO: OpenSSL 1.0.2l  25 May 2017


[2022-04-25T19:25:13] INFO: accepted secure socket


[2022-04-25T19:25:13] INFO: AES256-GCM-SHA384       TLSv1.2 Kx=RSA      Au=RSA  Enc=AESGCM(256) Mac=AEAD



[2022-04-25T19:25:13] NOTE: accepted client connection


[2022-04-25T19:25:13] NOTE: client "boblap" has connected


[2022-04-25T19:25:13] INFO: OpenSSL 1.0.2l  25 May 2017


[2022-04-25T19:25:14] INFO: accepted secure socket


[2022-04-25T19:25:14] INFO: AES256-GCM-SHA384       TLSv1.2 Kx=RSA      Au=RSA  Enc=AESGCM(256) Mac=AEAD



[2022-04-25T19:25:14] NOTE: accepted client connection


[2022-04-25T19:25:14] WARNING: a client with name "boblap" is already connected


[2022-04-25T19:25:14] NOTE: disconnecting client "boblap"


[2022-04-25T19:25:14] NOTE: client "boblap" has disconnected


[2022-04-25T19:25:14] INFO: OpenSSL 1.0.2l  25 May 2017


[2022-04-25T19:25:14] INFO: accepted secure socket


[2022-04-25T19:25:14] INFO: AES256-GCM-SHA384       TLSv1.2 Kx=RSA      Au=RSA  Enc=AESGCM(256) Mac=AEAD



[2022-04-25T19:25:14] NOTE: accepted client connection


[2022-04-25T19:25:14] WARNING: a client with name "boblap" is already connected


[2022-04-25T19:25:14] NOTE: disconnecting client "boblap"


[2022-04-25T19:25:14] NOTE: client "boblap" has disconnected


[2022-04-25T19:25:15] INFO: OpenSSL 1.0.2l  25 May 2017


[2022-04-25T19:25:15] INFO: accepted secure socket


[2022-04-25T19:25:15] INFO: AES256-GCM-SHA384       TLSv1.2 Kx=RSA      Au=RSA  Enc=AESGCM(256) Mac=AEAD



[2022-04-25T19:25:15] NOTE: accepted client connection


[2022-04-25T19:25:15] WARNING: a client with name "boblap" is already connected

etc...

Then, every now and then theres a...


[2022-04-25T19:25:10] WARNING: detected application not running, pid=2676
[2022-04-25T19:25:11] INFO: backing off, wait=2s, failures=1
[2022-04-25T19:25:13] INFO: starting new process as privileged user
[2022-04-25T19:25:13] INFO: drag and drop enabled

I suspect this is when barrier kills input for the host machine.

Log attached for reference.

barrier.log

@Vigrond commented on GitHub (Apr 26, 2022): update... it seems Ubuntu keeps starting new barrierc processes over time. I found 3 concurrent barrierc processes with the no tray option. In the windows log they were all competing as they were the same client name. So most of the log looks like this: ``` started server (IPv4/IPv6), waiting for clients server status: active [2022-04-25T19:25:13] INFO: OpenSSL 1.0.2l 25 May 2017 [2022-04-25T19:25:13] INFO: accepted secure socket [2022-04-25T19:25:13] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD [2022-04-25T19:25:13] NOTE: accepted client connection [2022-04-25T19:25:13] NOTE: client "boblap" has connected [2022-04-25T19:25:13] INFO: OpenSSL 1.0.2l 25 May 2017 [2022-04-25T19:25:14] INFO: accepted secure socket [2022-04-25T19:25:14] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD [2022-04-25T19:25:14] NOTE: accepted client connection [2022-04-25T19:25:14] WARNING: a client with name "boblap" is already connected [2022-04-25T19:25:14] NOTE: disconnecting client "boblap" [2022-04-25T19:25:14] NOTE: client "boblap" has disconnected [2022-04-25T19:25:14] INFO: OpenSSL 1.0.2l 25 May 2017 [2022-04-25T19:25:14] INFO: accepted secure socket [2022-04-25T19:25:14] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD [2022-04-25T19:25:14] NOTE: accepted client connection [2022-04-25T19:25:14] WARNING: a client with name "boblap" is already connected [2022-04-25T19:25:14] NOTE: disconnecting client "boblap" [2022-04-25T19:25:14] NOTE: client "boblap" has disconnected [2022-04-25T19:25:15] INFO: OpenSSL 1.0.2l 25 May 2017 [2022-04-25T19:25:15] INFO: accepted secure socket [2022-04-25T19:25:15] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD [2022-04-25T19:25:15] NOTE: accepted client connection [2022-04-25T19:25:15] WARNING: a client with name "boblap" is already connected ``` etc... Then, every now and then theres a... ``` [2022-04-25T19:25:10] WARNING: detected application not running, pid=2676 [2022-04-25T19:25:11] INFO: backing off, wait=2s, failures=1 [2022-04-25T19:25:13] INFO: starting new process as privileged user [2022-04-25T19:25:13] INFO: drag and drop enabled ``` I suspect this is when barrier kills input for the host machine. Log attached for reference. [barrier.log](https://github.com/debauchee/barrier/files/8559302/barrier.log)

gitea-mirror commented

2026-05-05 07:37:01 -06:00

Author

Owner

@yllekz commented on GitHub (May 2, 2022):

I'm running into a similar issue. My Linux Mint desktop is the server, and I have a Windows laptop as a client. When I shut down the Windows laptop, I am unable to use the mouse/keyboard on the desktop/server until I SSH in via another device, open htop, and kill all barrier processes, including one that ratchets the CPU past 100%.

@yllekz commented on GitHub (May 2, 2022): I'm running into a similar issue. My Linux Mint desktop is the server, and I have a Windows laptop as a client. When I shut down the Windows laptop, I am unable to use the mouse/keyboard on the desktop/server until I SSH in via another device, open htop, and kill all barrier processes, including one that ratchets the CPU past 100%.

No labels

Rows
Columns