[GH-ISSUE #1255] Client disconnects suddenly #1013

New issue

Open

opened 2026-05-05 07:23:04 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 07:23:04 -06:00

Owner

Originally created by @8-bit-memories on GitHub (Aug 20, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1255

Describe the bug
Both with Synergy 1.8.8, and now with Barrier 2.3.3.

While the Linux server is feeding keystroke and mouse movements to the Windows client, at random intervals the mouse and keyboard will jump back to the server
.

When that happens, the server's log looks like this:

[2021-08-20T08:26:08] WARNING: error writing to client "CLIENT"
[2021-08-20T08:26:08] INFO: jump from "CLIENT" to "SERVER" at 720,450
[2021-08-20T08:26:08] INFO: entering screen

and the client's log looks like this:

[2021-08-20T08:26:08] INFO: leaving screen
[2021-08-20T08:26:08] NOTE: disconnected from server
[2021-08-20T08:26:10] NOTE: connecting to 'SERVER.local': 192.168.1.62:24800
To Reproduce

Start it up and use, after some time, it happens. The key entry in the server-side log is "WARNING: error writing to client".

Expected behavior
The client should stay connected.

Screenshots

Desktop (please complete the following information):

OS: Server: Devuan Linux Chimaera. Client: Windows 10.
Barrier version 2.3.3

Additional context

Attached files are from client and server around an example occurrence of the symptom.

Is this an issue with the Windows host's intrusion protection software (which I cannot control)?
server.log
client.log

The symptom in the logs is at this time stamp:
[2021-08-20T10:35:13] WARNING: error writing to client "CLIENT"

Originally created by @8-bit-memories on GitHub (Aug 20, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1255 **Describe the bug** Both with Synergy 1.8.8, and now with Barrier 2.3.3. While the Linux server is feeding keystroke and mouse movements to the Windows client, at random intervals the mouse and keyboard will jump back to the server . When that happens, the server's log looks like this: [2021-08-20T08:26:08] WARNING: error writing to client "CLIENT" [2021-08-20T08:26:08] INFO: jump from "CLIENT" to "SERVER" at 720,450 [2021-08-20T08:26:08] INFO: entering screen and the client's log looks like this: [2021-08-20T08:26:08] INFO: leaving screen [2021-08-20T08:26:08] NOTE: disconnected from server [2021-08-20T08:26:10] NOTE: connecting to 'SERVER.local': 192.168.1.62:24800 **To Reproduce** Start it up and use, after some time, it happens. The key entry in the server-side log is "WARNING: error writing to client". **Expected behavior** The client should stay connected. **Screenshots** **Desktop (please complete the following information):** - OS: Server: Devuan Linux Chimaera. Client: Windows 10. - Barrier version 2.3.3 **Additional context** Attached files are from client and server around an example occurrence of the symptom. Is this an issue with the Windows host's intrusion protection software (which I cannot control)? [server.log](https://github.com/debauchee/barrier/files/7023220/server.log) [client.log](https://github.com/debauchee/barrier/files/7023221/client.log) The symptom in the logs is at this time stamp: [2021-08-20T10:35:13] WARNING: error writing to client "CLIENT"

gitea-mirror commented

2026-05-05 07:23:06 -06:00

Author

Owner

@8-bit-memories commented on GitHub (Aug 30, 2021):

This may be an issue with the server's wireless NIC, which was found to be disconnecting/connecting to the access point.

@8-bit-memories commented on GitHub (Aug 30, 2021): This may be an issue with the server's wireless NIC, which was found to be disconnecting/connecting to the access point.

gitea-mirror commented

2026-05-05 07:23:06 -06:00

Author

Owner

@8-bit-memories commented on GitHub (Sep 1, 2021):

The symptom still occurs after resolving the server's wireless NIC issue.

@8-bit-memories commented on GitHub (Sep 1, 2021): The symptom still occurs after resolving the server's wireless NIC issue.