github-starred/barrier
2
0
Fork 0
mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00
Code Issues 1.0k Projects Packages Wiki Activity Actions

[GH-ISSUE #1858] Barrier not work #1358

New issue
Open
opened 2026-05-05 07:45:13 -06:00 by gitea-mirror · 2 comments
gitea-mirror commented 2026-05-05 07:45:13 -06:00
Owner
Copy link

Originally created by @p6002 on GitHub (Dec 15, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1858

What happened?

Video:
https://streamable.com/wsuurk

I tried this software several years ago on other computers and it never worked (same problem).

Now I'm trying again with Win11 and Ububtu22 and again the same problem.
The cursor does not appear on the client and there is a problem returning the cursor to the server.

From what I understand it doesn't work for anyone? Has the software been abandoned forever? Are there any alternatives?

Version

v2.0.0-RC1

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?

Win11 as server, ubuntu client

Relevant log output

Server side:
######################

started server (IPv4/IPv6), waiting for clients
server status: active
[2022-12-15T16:47:17] NOTE: accepted client connection
[2022-12-15T16:47:17] NOTE: client "Tower-Terminal" has connected
[2022-12-15T16:47:26] INFO: switch from "Flow" to "Tower-Terminal" at 2003,1439
[2022-12-15T16:47:26] INFO: leaving screen
[2022-12-15T16:47:26] INFO: screen "Flow" updated clipboard 0
[2022-12-15T16:47:26] INFO: screen "Flow" updated clipboard 1
[2022-12-15T16:47:26] INFO: switch from "Tower-Terminal" to "Flow" at 1161,184
[2022-12-15T16:47:26] INFO: entering screen
[2022-12-15T16:47:27] INFO: switch from "Flow" to "Tower-Terminal" at 2559,1439
[2022-12-15T16:47:27] INFO: leaving screen
[2022-12-15T16:47:31] INFO: switch from "Tower-Terminal" to "Flow" at 1243,210
[2022-12-15T16:47:31] INFO: entering screen
[2022-12-15T16:47:31] INFO: switch from "Flow" to "Tower-Terminal" at 1,1439
[2022-12-15T16:47:31] INFO: leaving screen
[2022-12-15T16:47:31] INFO: switch from "Tower-Terminal" to "Flow" at 28,328
[2022-12-15T16:47:31] INFO: entering screen
[2022-12-15T16:47:32] INFO: switch from "Flow" to "Tower-Terminal" at 1753,1439
[2022-12-15T16:47:32] INFO: leaving screen
[2022-12-15T16:47:32] INFO: switch from "Tower-Terminal" to "Flow" at 1038,185
[2022-12-15T16:47:32] INFO: entering screen
[2022-12-15T16:47:41] INFO: switch from "Flow" to "Tower-Terminal" at 1415,1439
[2022-12-15T16:47:41] INFO: leaving screen
[2022-12-15T16:47:41] INFO: switch from "Tower-Terminal" to "Flow" at 867,190
[2022-12-15T16:47:41] INFO: entering screen
[2022-12-15T16:47:42] INFO: switch from "Flow" to "Tower-Terminal" at 1507,1439
[2022-12-15T16:47:42] INFO: leaving screen
[2022-12-15T16:47:42] INFO: switch from "Tower-Terminal" to "Flow" at 913,197
[2022-12-15T16:47:42] INFO: entering screen
[2022-12-15T16:47:44] INFO: switch from "Flow" to "Tower-Terminal" at 395,1439
[2022-12-15T16:47:44] INFO: leaving screen
[2022-12-15T16:47:44] INFO: switch from "Tower-Terminal" to "Flow" at 356,181
[2022-12-15T16:47:44] INFO: entering screen
[2022-12-15T16:47:45] INFO: switch from "Flow" to "Tower-Terminal" at 601,1439
[2022-12-15T16:47:45] INFO: leaving screen
[2022-12-15T16:47:45] INFO: switch from "Tower-Terminal" to "Flow" at 460,190
[2022-12-15T16:47:45] INFO: entering screen
[2022-12-15T16:47:45] INFO: switch from "Flow" to "Tower-Terminal" at 627,1439
[2022-12-15T16:47:45] INFO: leaving screen
[2022-12-15T16:47:45] INFO: switch from "Tower-Terminal" to "Flow" at 473,187
[2022-12-15T16:47:45] INFO: entering screen
[2022-12-15T16:47:46] INFO: switch from "Flow" to "Tower-Terminal" at 691,1439
[2022-12-15T16:47:46] INFO: leaving screen
[2022-12-15T16:47:46] INFO: switch from "Tower-Terminal" to "Flow" at 505,195
[2022-12-15T16:47:46] INFO: entering screen
[2022-12-15T16:47:47] INFO: switch from "Flow" to "Tower-Terminal" at 713,1439
[2022-12-15T16:47:47] INFO: leaving screen
[2022-12-15T16:47:47] INFO: switch from "Tower-Terminal" to "Flow" at 511,181
[2022-12-15T16:47:47] INFO: entering screen
[2022-12-15T16:47:48] INFO: switch from "Flow" to "Tower-Terminal" at 545,1439
[2022-12-15T16:47:48] INFO: leaving screen
[2022-12-15T16:47:48] INFO: switch from "Tower-Terminal" to "Flow" at 433,196
[2022-12-15T16:47:48] INFO: entering screen
[2022-12-15T16:47:49] INFO: switch from "Flow" to "Tower-Terminal" at 555,1439
[2022-12-15T16:47:49] INFO: leaving screen
[2022-12-15T16:47:49] INFO: switch from "Tower-Terminal" to "Flow" at 435,187
[2022-12-15T16:47:49] INFO: entering screen
[2022-12-15T16:47:50] INFO: switch from "Flow" to "Tower-Terminal" at 615,1439
[2022-12-15T16:47:50] INFO: leaving screen
[2022-12-15T16:47:50] INFO: switch from "Tower-Terminal" to "Flow" at 468,191
[2022-12-15T16:47:50] INFO: entering screen
[2022-12-15T16:47:51] INFO: switch from "Flow" to "Tower-Terminal" at 701,1439
[2022-12-15T16:47:51] INFO: leaving screen
[2022-12-15T16:47:51] INFO: switch from "Tower-Terminal" to "Flow" at 508,178
[2022-12-15T16:47:51] INFO: entering screen


Client side:
######################


[2022-12-15T16:31:51] NOTE: connecting to '192.168.1.161': 192.168.1.161:24800
connected to server
[2022-12-15T16:32:58] INFO: entering screen
[2022-12-15T16:32:58] INFO: clipboard was updated
[2022-12-15T16:32:58] INFO: clipboard was updated
[2022-12-15T16:32:58] INFO: leaving screen
[2022-12-15T16:32:58] INFO: entering screen
[2022-12-15T16:33:01] INFO: leaving screen
[2022-12-15T16:33:01] INFO: entering screen
[2022-12-15T16:33:01] INFO: leaving screen
[2022-12-15T16:34:48] INFO: entering screen
[2022-12-15T16:34:48] INFO: leaving screen
[2022-12-15T16:34:49] INFO: entering screen
[2022-12-15T16:34:52] INFO: leaving screen
[2022-12-15T16:34:54] INFO: entering screen
[2022-12-15T16:34:54] INFO: leaving screen
[2022-12-15T16:46:03] INFO: entering screen
[2022-12-15T16:46:03] INFO: leaving screen
[2022-12-15T16:46:03] INFO: entering screen
[2022-12-15T16:46:03] INFO: leaving screen
[2022-12-15T16:46:04] INFO: entering screen

Any other information

No response

Originally created by @p6002 on GitHub (Dec 15, 2022). Original GitHub issue: https://github.com/debauchee/barrier/issues/1858 ### What happened? Video: https://streamable.com/wsuurk I tried this software several years ago on other computers and it never worked (same problem). Now I'm trying again with Win11 and Ububtu22 and again the same problem. The cursor does not appear on the client and there is a problem returning the cursor to the server. From what I understand it doesn't work for anyone? Has the software been abandoned forever? Are there any alternatives? ### Version v2.0.0-RC1 ### 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? Win11 as server, ubuntu client ### Relevant log output ```shell Server side: ###################### started server (IPv4/IPv6), waiting for clients server status: active [2022-12-15T16:47:17] NOTE: accepted client connection [2022-12-15T16:47:17] NOTE: client "Tower-Terminal" has connected [2022-12-15T16:47:26] INFO: switch from "Flow" to "Tower-Terminal" at 2003,1439 [2022-12-15T16:47:26] INFO: leaving screen [2022-12-15T16:47:26] INFO: screen "Flow" updated clipboard 0 [2022-12-15T16:47:26] INFO: screen "Flow" updated clipboard 1 [2022-12-15T16:47:26] INFO: switch from "Tower-Terminal" to "Flow" at 1161,184 [2022-12-15T16:47:26] INFO: entering screen [2022-12-15T16:47:27] INFO: switch from "Flow" to "Tower-Terminal" at 2559,1439 [2022-12-15T16:47:27] INFO: leaving screen [2022-12-15T16:47:31] INFO: switch from "Tower-Terminal" to "Flow" at 1243,210 [2022-12-15T16:47:31] INFO: entering screen [2022-12-15T16:47:31] INFO: switch from "Flow" to "Tower-Terminal" at 1,1439 [2022-12-15T16:47:31] INFO: leaving screen [2022-12-15T16:47:31] INFO: switch from "Tower-Terminal" to "Flow" at 28,328 [2022-12-15T16:47:31] INFO: entering screen [2022-12-15T16:47:32] INFO: switch from "Flow" to "Tower-Terminal" at 1753,1439 [2022-12-15T16:47:32] INFO: leaving screen [2022-12-15T16:47:32] INFO: switch from "Tower-Terminal" to "Flow" at 1038,185 [2022-12-15T16:47:32] INFO: entering screen [2022-12-15T16:47:41] INFO: switch from "Flow" to "Tower-Terminal" at 1415,1439 [2022-12-15T16:47:41] INFO: leaving screen [2022-12-15T16:47:41] INFO: switch from "Tower-Terminal" to "Flow" at 867,190 [2022-12-15T16:47:41] INFO: entering screen [2022-12-15T16:47:42] INFO: switch from "Flow" to "Tower-Terminal" at 1507,1439 [2022-12-15T16:47:42] INFO: leaving screen [2022-12-15T16:47:42] INFO: switch from "Tower-Terminal" to "Flow" at 913,197 [2022-12-15T16:47:42] INFO: entering screen [2022-12-15T16:47:44] INFO: switch from "Flow" to "Tower-Terminal" at 395,1439 [2022-12-15T16:47:44] INFO: leaving screen [2022-12-15T16:47:44] INFO: switch from "Tower-Terminal" to "Flow" at 356,181 [2022-12-15T16:47:44] INFO: entering screen [2022-12-15T16:47:45] INFO: switch from "Flow" to "Tower-Terminal" at 601,1439 [2022-12-15T16:47:45] INFO: leaving screen [2022-12-15T16:47:45] INFO: switch from "Tower-Terminal" to "Flow" at 460,190 [2022-12-15T16:47:45] INFO: entering screen [2022-12-15T16:47:45] INFO: switch from "Flow" to "Tower-Terminal" at 627,1439 [2022-12-15T16:47:45] INFO: leaving screen [2022-12-15T16:47:45] INFO: switch from "Tower-Terminal" to "Flow" at 473,187 [2022-12-15T16:47:45] INFO: entering screen [2022-12-15T16:47:46] INFO: switch from "Flow" to "Tower-Terminal" at 691,1439 [2022-12-15T16:47:46] INFO: leaving screen [2022-12-15T16:47:46] INFO: switch from "Tower-Terminal" to "Flow" at 505,195 [2022-12-15T16:47:46] INFO: entering screen [2022-12-15T16:47:47] INFO: switch from "Flow" to "Tower-Terminal" at 713,1439 [2022-12-15T16:47:47] INFO: leaving screen [2022-12-15T16:47:47] INFO: switch from "Tower-Terminal" to "Flow" at 511,181 [2022-12-15T16:47:47] INFO: entering screen [2022-12-15T16:47:48] INFO: switch from "Flow" to "Tower-Terminal" at 545,1439 [2022-12-15T16:47:48] INFO: leaving screen [2022-12-15T16:47:48] INFO: switch from "Tower-Terminal" to "Flow" at 433,196 [2022-12-15T16:47:48] INFO: entering screen [2022-12-15T16:47:49] INFO: switch from "Flow" to "Tower-Terminal" at 555,1439 [2022-12-15T16:47:49] INFO: leaving screen [2022-12-15T16:47:49] INFO: switch from "Tower-Terminal" to "Flow" at 435,187 [2022-12-15T16:47:49] INFO: entering screen [2022-12-15T16:47:50] INFO: switch from "Flow" to "Tower-Terminal" at 615,1439 [2022-12-15T16:47:50] INFO: leaving screen [2022-12-15T16:47:50] INFO: switch from "Tower-Terminal" to "Flow" at 468,191 [2022-12-15T16:47:50] INFO: entering screen [2022-12-15T16:47:51] INFO: switch from "Flow" to "Tower-Terminal" at 701,1439 [2022-12-15T16:47:51] INFO: leaving screen [2022-12-15T16:47:51] INFO: switch from "Tower-Terminal" to "Flow" at 508,178 [2022-12-15T16:47:51] INFO: entering screen Client side: ###################### [2022-12-15T16:31:51] NOTE: connecting to '192.168.1.161': 192.168.1.161:24800 connected to server [2022-12-15T16:32:58] INFO: entering screen [2022-12-15T16:32:58] INFO: clipboard was updated [2022-12-15T16:32:58] INFO: clipboard was updated [2022-12-15T16:32:58] INFO: leaving screen [2022-12-15T16:32:58] INFO: entering screen [2022-12-15T16:33:01] INFO: leaving screen [2022-12-15T16:33:01] INFO: entering screen [2022-12-15T16:33:01] INFO: leaving screen [2022-12-15T16:34:48] INFO: entering screen [2022-12-15T16:34:48] INFO: leaving screen [2022-12-15T16:34:49] INFO: entering screen [2022-12-15T16:34:52] INFO: leaving screen [2022-12-15T16:34:54] INFO: entering screen [2022-12-15T16:34:54] INFO: leaving screen [2022-12-15T16:46:03] INFO: entering screen [2022-12-15T16:46:03] INFO: leaving screen [2022-12-15T16:46:03] INFO: entering screen [2022-12-15T16:46:03] INFO: leaving screen [2022-12-15T16:46:04] INFO: entering screen ``` ### Any other information _No response_
gitea-mirror commented 2026-05-05 07:45:15 -06:00
Author
Owner
Copy link

@eaoporto commented on GitHub (Dec 15, 2022):

Hey! I'm unsure of the current state of Barrier with Windows 11 and Ubuntu 22, unfortunately. However, I can report that I discovered Barrier about 2 weeks ago, and have been daily driving it at work and at home between Windows 10 and macOS 13.0.1 and macOS 13.1. My Desktop at home is a newer, custom built 12th Gen Intel system. The Desktop at work is an older HP 3rd Gen Intel system. Works exactly the same on both Windows machines. My macOS machine is an Apple Silicon Macbook Pro 14" M1 Pro based machine. In macOS, in Activity Monitor, when viewing CPU Processes, under Kind, Barrier is listed as "Intel" and not "Apple". So my Macbook Pro is using Rosetta to translate and run Barrier. It is not running "natively".

The Build Version and Build Date is showing as the same across both Windows machines and my Macbook Pro. Downloaded and installed Barrier from the build executables here on Github. I did not compile it myself.
Build Version: 2.4.0-release-3e0d758b
Build Date: November 1, 2021

When using it at work, in order to work properly, on the client side I need to manually configure and set the IP Address of the Server side. At home, it automatically configures and sees my Desktop.

I've only run into the following issues:

  1. Drag and Drop file sharing has never worked for me, across any machine or configuration, no matter how hard I try. This isn't an issue for me, my main use with Barrier is simply shared mouse and keyboard controls. File Sharing via Drag and Drop wasn't an interest for me, but I can understand how it could be a deal breaker for others.

  2. Updating my Macbook Pro from Ventura 13.01 to Ventura 13.1 caused issue with the Privacy and Security -> Accessibility settings to break, even though it was still set and was allowed access to control the computer. I had to delete the entry in Accessibility all together, and add it again when trying to start Barrier. Quick and easy fix, and it works as normal again. If I have to do that every update, I don't mind.

  3. Waking from sleep is wonky, but that doesn't surprise me. If either the server goes to sleep, or the client goes to sleep, upon wake, sometimes Barrier needs to be restarted. When it does, it requires restarting the application on both machines, client and server side, to function again. Sometimes, it does not require restarting, and upon wake it will still function perfectly fine. This is an issue I have had will all three machines I previously mentioned.

The issues I have had with it are easy to manage for me, and they're more a nuisance than anything. I have still been using it regardless and it has proven to be very valuable in terms of productivity and ease of use of my machines, both at home and at work. I absolutely love it, and I really hope it keeps living on! I know absolutely nothing when it comes to coding, but I am more than willing to try things on different machines and report my findings to help others.

<!-- gh-comment-id:1353540062 --> @eaoporto commented on GitHub (Dec 15, 2022): Hey! I'm unsure of the current state of Barrier with Windows 11 and Ubuntu 22, unfortunately. However, I can report that I discovered Barrier about 2 weeks ago, and have been daily driving it at work and at home between Windows 10 and macOS 13.0.1 and macOS 13.1. My Desktop at home is a newer, custom built 12th Gen Intel system. The Desktop at work is an older HP 3rd Gen Intel system. Works exactly the same on both Windows machines. My macOS machine is an Apple Silicon Macbook Pro 14" M1 Pro based machine. In macOS, in Activity Monitor, when viewing CPU Processes, under Kind, Barrier is listed as "Intel" and not "Apple". So my Macbook Pro is using Rosetta to translate and run Barrier. It is not running "natively". The Build Version and Build Date is showing as the same across both Windows machines and my Macbook Pro. Downloaded and installed Barrier from the build executables here on Github. I did not compile it myself. Build Version: 2.4.0-release-3e0d758b Build Date: November 1, 2021 When using it at work, in order to work properly, on the client side I need to manually configure and set the IP Address of the Server side. At home, it automatically configures and sees my Desktop. I've only run into the following issues: 1) Drag and Drop file sharing **has never worked for me**, across any machine or configuration, no matter how hard I try. This isn't an issue for me, my main use with Barrier is simply shared mouse and keyboard controls. File Sharing via Drag and Drop wasn't an interest for me, but I can understand how it could be a deal breaker for others. 2) Updating my Macbook Pro from Ventura 13.01 to Ventura 13.1 caused issue with the Privacy and Security -> Accessibility settings to break, even though it was still set and was allowed access to control the computer. I had to delete the entry in Accessibility all together, and add it again when trying to start Barrier. Quick and easy fix, and it works as normal again. If I have to do that every update, I don't mind. 3) Waking from sleep is wonky, but that doesn't surprise me. If either the server goes to sleep, or the client goes to sleep, upon wake, _sometimes_ Barrier needs to be restarted. When it does, it requires restarting the application on both machines, client and server side, to function again. Sometimes, it does not require restarting, and upon wake it will still function perfectly fine. This is an issue I have had will all three machines I previously mentioned. The issues I have had with it are easy to manage for me, and they're more a nuisance than anything. I have still been using it regardless and it has proven to be very valuable in terms of productivity and ease of use of my machines, both at home and at work. I absolutely love it, and I really hope it keeps living on! I know absolutely nothing when it comes to coding, but I am more than willing to try things on different machines and report my findings to help others.
gitea-mirror commented 2026-05-05 07:45:17 -06:00
Author
Owner
Copy link

@timriker commented on GitHub (Feb 11, 2023):

Suspect dupe of #1713

Try running windows displays at 100% or revert to 2.3.4

<!-- gh-comment-id:1426641299 --> @timriker commented on GitHub (Feb 11, 2023): Suspect dupe of #1713 Try running windows displays at 100% or revert to 2.3.4
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
enhancement/builds/windows-multi-versions-build
martin-furter-barrier-term
enhancement/builds/macos-universal
enhancement/builds/macos-universal-qt6-test
2.3.x
fix/lang-translation/ssl-slash-tls
feature/build/compile/32-bit
feature/build/compile/armv7
testing-framework
README-update
remotes/fork/README-update
remotes/fork/smartzeroconf
smartzeroconf
pages-devel
remotes/fork/pages-devel
pkgconfig
remotes/fork/pkgconfig
release
remotes/fork/release
v2.4.0
v2.3.4
v2.3.3
1.11.0-stable
v1.11.0-rc2
v2.3.2
v1.10.3-stable
v2.3.2-alpha
v2.3.1
v2.3.0
v1.10.2-stable
v1.10.2-rc1
v1.10.2-rc2
v2.1.2
v2.0.8-beta
v2.0.7-beta
v2.0.4-beta
v2.0.3-beta
v2.1.1
v2.1.0
v1.9.1-stable
v2.0.0
v1.9.0-stable
v2.0.0-RC2
v2.0.0-RC1
v2.0.0-stable
v1.8.8-stable
v1.8.7-stable
v1.8.6-stable
v1.8.5-stable
v1.8.4-stable
v1.8.3-stable
v1.8.1-stable
v1.8.0-beta
v1.7.3-stable
v1.7.2-stable
v1.7.1-stable
1.7.0
1.6.3-final
1.6.2
1.6.1
1.6.0
Labels
Clear labels   
HiDPI

   
bounty

   
bsd/freebsd

   
bsd/openbsd

   
bug

   
bug

   
build-infra

   
cantfix

   
critical

   
doc

   
duplicate

   
enhancement

   
fix-available

   
from git

   
from release

   
good first issue

   
help wanted

   
installer/package

   
invalid

   
linux

   
macOS

   
meta

   
needs testing

   
pull-request

Mirrored from GitHub Pull Request

  
query

   
question

   
regression

   
regression

   
v2.4.0

   
windows

   
wontfix

   
work-in-progress
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#1358
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?