mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 22:01:23 -06:00
[GH-ISSUE #474] Not working in MacOS Catalina #369
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#369
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @luizfilho00 on GitHub (Oct 21, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/474
After updating do MacOS Catalina the application stopped to work.
@shymega commented on GitHub (Oct 21, 2019):
Can you please provide further information? We have an issue template precisely for that purpose. Your bug report is very sparse, and just saying "it does't work" provides us with no information about what your issue is. I'm going to mark this issue as invalid and close it within 48 hours if we don't hear back from you. In future, please do fill out the template...
@mandusm commented on GitHub (Oct 21, 2019):
I believe I have the same issue as this user. It seems like barrier requires the
shapplication to control the computer.@shymega commented on GitHub (Oct 21, 2019):
@mandusm The thing is, this user has provided zero information as to what their issue is. You may well have the same issue, but I would urge caution at this time - let's keep the two issues separate until we have further information. Thank you for opening #475.
@luizfilho00 commented on GitHub (Oct 24, 2019):
Problem was solved adding "sh" to accessibility permissions!
@AdrianKoshka commented on GitHub (Oct 24, 2019):
If the problem was solved, why was the issue re-opened?
@shymega commented on GitHub (Oct 26, 2019):
@luizfilho00 Did you mean to reopen this issue? If you didn't, please close the issue, or you can leave it, and I'll close it later on this week. Cheers.
@loren-osborn commented on GitHub (Jan 15, 2020):
Can anyone confirm Barrier KVM working in macOS Catalina; even anecdotally?
(While it would be best to know Barrier works with Catalina for everyone, it would still be helpful to know if it's working for anyone.)
@jpdante commented on GitHub (Feb 11, 2020):
@loren-osborn I can confirm that Barrier KVM is running on Mac OS Catalina (Server and Client) with Windows 10 Build 1909
However, performing the installation was a bit strange, the software did not want to connect at the beginning but when restarting both systems they connected.
@public commented on GitHub (Mar 23, 2020):
It did work for me for a while but has recently stopped working.
The client (OS X) and server (Windows 10) connect to each other just fine but no mouse inputs seem to make it across to OS X. Keyboard inputs do seem to be working OK though. I've added many things to my accessibility whitelist. sh, barrier, barriers, barrier.sh, barrierc, Barrier.app etc but it doesn't seem to help. Even running as root has no effect.
In the client log there are warnings about "cursor may not be visible" but nothing that suggests why it might not be.
@donrudo commented on GitHub (Mar 30, 2020):
I confirm is not working for me since Catalina got released, I am using it from Catalina to Catalina, mouse works fine (with the normal limitations for gestures) but keyboard is not working.
@azemute commented on GitHub (May 5, 2020):
I can confirm that I was able to get Barrier to work in server mode with a Windows client attached by doing the following on the Mac server:
/binshand dragging it into the "Security and Privacy" apps section and ensuring it remains checkedAfter performing these steps, barrier is working and allowing me to share my keyboard and mouse as normal
@plessbd commented on GitHub (May 5, 2020):
using #648 you can build an up to date release that has updated fixes for this that have it show up as Barrier instead of sh
Or if you trust people https://github.com/simons-public/barrier/releases/tag/use-macdeployqt has a release already built
@simons-public commented on GitHub (May 5, 2020):
As @plessbd mentioned this has been fixed. Pull request #487. @azemute It’s pretty unsafe to give sh accessibility privileges, I don’t think it’s a good idea to recommend that as a fix for this issue. Maybe the devs can post a new release for all the Catalina users.
@donrudo commented on GitHub (May 6, 2020):
Tried the @plessbd proposal by reinstalled barrier and once the privileges were set reinstalled the official build; the process worked for a few minutes and then the keyboard stop working again.
The current accessibility privileges in both computers show barrier, barriers, barrier.sh, barrierc and sh enabled while testing, I agree with @simons-public allowing sh is really unsafe and should be done only to test if the issue is a privilege issue.