github-starred/barrier

Fork 0

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

[GH-ISSUE #1085] Clipboard sync stops functioning eventually #867

New issue

Open

opened 2026-05-05 07:13:55 -06:00 by gitea-mirror · 7 comments

gitea-mirror commented

2026-05-05 07:13:55 -06:00

Owner

Originally created by @Ruthalas on GitHub (Mar 3, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1085

Describe the bug
I use the application daily, and leave it running. Every few hours, the clipboard sync simply stops functioning. Stopping and starting the service restores functionality. (I needn't re-copy the item, it propagates the existing clipboard contents on stop/start.)

This issue occurs with both copied images and text.

To Reproduce
Steps to reproduce the behavior:

Set up two windows PCs connected via ethernet
Set up barrier on them
Link and use barrier with them
Wait several hours

Expected behavior
Clipboard sync will continue to function while computers are linked

Desktop (please complete the following information):
OS: Windows 10 Pro x64 (19042.804)
Barrier: 2.3.3-reease-3395cca9

Additional context
Re-copying the same item again does not resolve the issue. (Unlike Issue 1053)
I do not believe this issue is a duplicate of Issue 1074 because the target machine does not receive the clipboard at all.

I can provide logs if desired.

Originally created by @Ruthalas on GitHub (Mar 3, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1085 **Describe the bug** I use the application daily, and leave it running. Every few hours, the clipboard sync simply stops functioning. Stopping and starting the service restores functionality. (I needn't re-copy the item, it propagates the existing clipboard contents on stop/start.) This issue occurs with both copied images and text. **To Reproduce** Steps to reproduce the behavior: 1. Set up two windows PCs connected via ethernet 2. Set up barrier on them 3. Link and use barrier with them 4. Wait several hours **Expected behavior** Clipboard sync will continue to function while computers are linked **Desktop (please complete the following information):** OS: Windows 10 Pro x64 (19042.804) Barrier: 2.3.3-reease-3395cca9 **Additional context** Re-copying the same item again does not resolve the issue. (Unlike Issue 1053) I do not believe this issue is a duplicate of Issue 1074 because the target machine does not receive the clipboard at all. I can provide logs if desired.

gitea-mirror commented

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

Author

Owner

@chewi commented on GitHub (Apr 8, 2021):

I get this about once or twice a day between Linux (server) and Windows (client).

@chewi commented on GitHub (Apr 8, 2021): I get this about once or twice a day between Linux (server) and Windows (client).

gitea-mirror commented

2026-05-05 07:13:59 -06:00

Author

Owner

@lihexin88 commented on GitHub (Aug 12, 2021):

I get this about once or twice a day between Linux (server) and Windows (client).

sames to me ...... can anyone help ?

@lihexin88 commented on GitHub (Aug 12, 2021): > I get this about once or twice a day between Linux (server) and Windows (client). sames to me ...... can anyone help ?

gitea-mirror commented

2026-05-05 07:14:00 -06:00

Author

Owner

@redsigma commented on GitHub (Oct 1, 2021):

For me it happens only when copying from server to client. Copyign from client to server works.

I can fix it by reloading the server. I think a good start would be to add an item for restarting, in the taskbar icon so it's easier to restart

@redsigma commented on GitHub (Oct 1, 2021): For me it happens only when copying from server to client. Copyign from client to server works. I can fix it by reloading the server. I think a good start would be to add an item for restarting, in the taskbar icon so it's easier to restart

gitea-mirror commented

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

Author

Owner

@timtait commented on GitHub (Oct 7, 2021):

Exactly the same thing for me between Windows10 server and Mac client.

Has happened forever, restarting the server makes it work again.

@timtait commented on GitHub (Oct 7, 2021): Exactly the same thing for me between Windows10 server and Mac client. Has happened forever, restarting the server makes it work again.

gitea-mirror commented

2026-05-05 07:14:02 -06:00

Author

Owner

@redsigma commented on GitHub (Oct 7, 2021):

Exactly the same thing for me between Windows10 server and Mac client.

Has happened forever, restarting the server makes it work again.

I too use windows (server) and linux (client). At some point this problem, happened on client but restarting the server fixed it still fixed it.

@redsigma commented on GitHub (Oct 7, 2021): > > > Exactly the same thing for me between Windows10 server and Mac client. > > Has happened forever, restarting the server makes it work again. I too use windows (server) and linux (client). At some point this problem, happened on client but restarting the server fixed it still fixed it.

gitea-mirror commented

2026-05-05 07:14:03 -06:00

Author

Owner

@inominate commented on GitHub (Oct 13, 2021):

This is a bug that has been around for nearly 20 years, since the early days of synergy.

@inominate commented on GitHub (Oct 13, 2021): This is a bug that has been around for nearly 20 years, since the early days of synergy.

gitea-mirror commented

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

Author

Owner

@JDNdeveloper commented on GitHub (Oct 28, 2021):

A daily frustration...hopefully this is fixed someday.

@JDNdeveloper commented on GitHub (Oct 28, 2021): A daily frustration...hopefully this is fixed someday.