github-starred/barrier

Fork 0

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

[GH-ISSUE #958] Barrier not starting up on macOS Big Sur 11.0.1 #769

New issue

Open

opened 2026-05-05 07:03:04 -06:00 by gitea-mirror · 13 comments

gitea-mirror commented

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

Owner

Originally created by @raffimohammed on GitHub (Nov 24, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/958

Describe the bug
Barrier not starting up after upgrading to macOS Big Sur 11.0.1

To Reproduce
Start the Barrier application

Steps to reproduce the behavior:
Start the Barrier application

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Please do not link to image hosting sites, as these can be ephemeral. Instead, attach them to the issue.

Desktop (please complete the following information):

OS: [macOS Big Sur]
Barrier version [2.3.3]

Additional context
Error logged in /var/log/system.log:
Nov 24 06:38:08 computer1 com.apple.xpc.launchd[1] (application.barrier.51427154.51427160[6700]): Service exited with abnormal code: 1

Add any other context about the problem here.

Originally created by @raffimohammed on GitHub (Nov 24, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/958 **Describe the bug** Barrier not starting up after upgrading to macOS Big Sur 11.0.1 **To Reproduce** Start the Barrier application Steps to reproduce the behavior: Start the Barrier application **Expected behavior** A clear and concise description of what you expected to happen. **Screenshots** If applicable, add screenshots to help explain your problem. Please do not link to image hosting sites, as these can be ephemeral. Instead, attach them to the issue. **Desktop (please complete the following information):** - OS: [macOS Big Sur] - Barrier version [2.3.3] **Additional context** Error logged in /var/log/system.log: Nov 24 06:38:08 computer1 com.apple.xpc.launchd[1] (application.barrier.51427154.51427160[6700]): Service exited with abnormal code: 1 Add any other context about the problem here.

gitea-mirror commented

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

Author

Owner

@senf666 commented on GitHub (Nov 25, 2020):

working fine on this Big Sur installation.

@senf666 commented on GitHub (Nov 25, 2020): working fine on this Big Sur installation.

gitea-mirror commented

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

Author

Owner

@kierandelaney commented on GitHub (Nov 27, 2020):

I had a very similar issue - eventually after a restart I started getting the prompt to grant Accessibility rights - which were already ticked. Whatever I did, app launch triggered this request. I unticked and removed the app, started it, granted permission again and it finally opened. I am not sure what happened to the permissions, it was like Barrier couldn't see they were already set. 🤷‍♂️

Might be completely different, but I also had the same system log entries before the restart.

@kierandelaney commented on GitHub (Nov 27, 2020): I had a very similar issue - eventually after a restart I started getting the prompt to grant Accessibility rights - which were already ticked. Whatever I did, app launch triggered this request. I unticked and removed the app, started it, granted permission again and it finally opened. I am not sure what happened to the permissions, it was like Barrier couldn't see they were already set. 🤷‍♂️ Might be completely different, but I also had the same system log entries before the restart.

gitea-mirror commented

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

Author

Owner

@raffimohammed commented on GitHub (Nov 27, 2020):

Restart did not help. I uninstalled and installed the application which prompted me for Barrier to use Accessibility privileges (Settings --> Security & Privacy --> Accessibility). I unticked and removed the older application; and gave access to the newer application. Then I was able to start the application.

Here is the log after the successful launch of the application.

Nov 27 10:48:49 computer1 com.apple.xpc.launchd[1]: Coalition Cache Hit: app<application.barrier.64501363.64501490(501)> [5871]

@raffimohammed commented on GitHub (Nov 27, 2020): Restart did not help. I uninstalled and installed the application which prompted me for Barrier to use Accessibility privileges (Settings --> Security & Privacy --> Accessibility). I unticked and removed the older application; and gave access to the newer application. Then I was able to start the application. Here is the log after the successful launch of the application. Nov 27 10:48:49 computer1 com.apple.xpc.launchd[1]: Coalition Cache Hit: app<application.barrier.64501363.64501490(501)> [5871]

gitea-mirror commented

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

Author

Owner

@kierandelaney commented on GitHub (Nov 30, 2020):

I upgraded a second system at the weekend to Big Sur and exactly the same thing happened. This time, I went straight to removing the permission and re-adding it to fix.

@kierandelaney commented on GitHub (Nov 30, 2020): I upgraded a second system at the weekend to Big Sur and exactly the same thing happened. This time, I went straight to removing the permission and re-adding it to fix.

gitea-mirror commented

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

Author

Owner

@jchien83 commented on GitHub (Dec 8, 2020):

On Big Sur 11.0.1 and Barrier v2.3.3 I am able to get the server running on macOS but when using the client it's stuck on Barrier is starting.

@jchien83 commented on GitHub (Dec 8, 2020): On Big Sur 11.0.1 and Barrier v2.3.3 I am able to get the server running on macOS but when using the client it's stuck on Barrier is starting.

gitea-mirror commented

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

Author

Owner

@raffimohammed commented on GitHub (Dec 9, 2020):

@jchien83, can you delete the client application's privileges (Settings --> Security & Privacy --> Accessibility)? Don't just uncheck and check back the checkbox beside the Barrier application logo. Delete it by using the "-" minus sign. When you restart the Barrier application it should prompt you to provide the application Accessibility privileges.

@raffimohammed commented on GitHub (Dec 9, 2020): @jchien83, can you delete the client application's privileges (Settings --> Security & Privacy --> Accessibility)? Don't just uncheck and check back the checkbox beside the Barrier application logo. Delete it by using the "-" minus sign. When you restart the Barrier application it should prompt you to provide the application Accessibility privileges.

gitea-mirror commented

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

Author

Owner

@jchien83 commented on GitHub (Dec 9, 2020):

@jchien83, can you delete the client application's privileges (Settings --> Security & Privacy --> Accessibility)? Don't just uncheck and check back the checkbox beside the Barrier application logo. Delete it by using the "-" minus sign. When you restart the Barrier application it should prompt you to provide the application Accessibility privileges.

I got it working. It helps if I look at the logs. It was complaining about the Macbook name being rejected.

@jchien83 commented on GitHub (Dec 9, 2020): > @jchien83, can you delete the client application's privileges (Settings --> Security & Privacy --> Accessibility)? Don't just uncheck and check back the checkbox beside the Barrier application logo. Delete it by using the "-" minus sign. When you restart the Barrier application it should prompt you to provide the application Accessibility privileges. I got it working. It helps if I look at the logs. It was complaining about the Macbook name being rejected.

gitea-mirror commented

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

Author

Owner

@JJFrampton commented on GitHub (Feb 4, 2021):

I had a very similar issue - eventually after a restart I started getting the prompt to grant Accessibility rights - which were already ticked. Whatever I did, app launch triggered this request. I unticked and removed the app, started it, granted permission again and it finally opened. I am not sure what happened to the permissions, it was like Barrier couldn't see they were already set.

Might be completely different, but I also had the same system log entries before the restart.

This worked for me instantly, thanks.

I didn't have to remove the the app, just unchecked it, then relaunched the app and granted permissions again.

👍

@JJFrampton commented on GitHub (Feb 4, 2021): > I had a very similar issue - eventually after a restart I started getting the prompt to grant Accessibility rights - which were already ticked. Whatever I did, app launch triggered this request. I unticked and removed the app, started it, granted permission again and it finally opened. I am not sure what happened to the permissions, it was like Barrier couldn't see they were already set. > > Might be completely different, but I also had the same system log entries before the restart. This worked for me instantly, thanks. I didn't have to remove the the app, just unchecked it, then relaunched the app and granted permissions again. :+1:

gitea-mirror commented

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

Author

Owner

@ericlowry commented on GitHub (May 22, 2021):

Ok, the trick for me was to un-tick the permissions and actually remove Barrier from the "Allow the apps below to control your computer" list. I clicked the minus button '-' at the bottom of the list to completely remove Barrier from the list altogether. And then I clicked the add button '+' (right next to minus) and added Barrier back into the list. Worked like a charm, no reboot required...

@ericlowry commented on GitHub (May 22, 2021): Ok, the trick for me was to un-tick the permissions and actually remove Barrier from the "Allow the apps below to control your computer" list. I clicked the minus button '-' at the bottom of the list to completely remove Barrier from the list altogether. And then I clicked the add button '+' (right next to minus) and added Barrier back into the list. Worked like a charm, no reboot required...

gitea-mirror commented

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

Author

Owner

@emacstheviking commented on GitHub (Jul 26, 2021):

Doesn't work for me, keeps saying 'Starting' but the client laptop won't connect, keeps on saying 'ERROR code 9'. I tried all the other remedies in this thread as well.

@emacstheviking commented on GitHub (Jul 26, 2021): Doesn't work for me, keeps saying 'Starting' but the client laptop won't connect, keeps on saying 'ERROR code 9'. I tried all the other remedies in this thread as well.

gitea-mirror commented

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

Author

Owner

@raffimohammed commented on GitHub (Jul 27, 2021):

Doesn't work for me, keeps saying 'Starting' but the client laptop won't connect, keeps on saying 'ERROR code 9'. I tried all the other remedies in this thread as well.

Can you connect to server_ip:24800 from the client laptop?

@raffimohammed commented on GitHub (Jul 27, 2021): > Doesn't work for me, keeps saying 'Starting' but the client laptop won't connect, keeps on saying 'ERROR code 9'. I tried all the other remedies in this thread as well. Can you connect to server_ip:24800 from the client laptop?

gitea-mirror commented

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

Author

Owner

@emacstheviking commented on GitHub (Jul 27, 2021):

No, I used to server to verify IP then on client I unticked auto config, entered 192.168.0.2:24800 and it still eventually timed out with error 9.
I have the Firewall disabled on both the client and the server.

@emacstheviking commented on GitHub (Jul 27, 2021): No, I used to server to verify IP then on client I unticked auto config, entered 192.168.0.2:24800 and it still eventually timed out with error 9. I have the Firewall disabled on both the client and the server.

gitea-mirror commented

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

Author

Owner

@raffimohammed commented on GitHub (Sep 3, 2021):

No, I used to server to verify IP then on client I unticked auto config, entered 192.168.0.2:24800 and it still eventually timed out with error 9.
I have the Firewall disabled on both the client and the server.

Can you ping 192.168.0.2 from the client? ..and nc -vz 192.168.0.2 24800 from the client?

@raffimohammed commented on GitHub (Sep 3, 2021): > No, I used to server to verify IP then on client I unticked auto config, entered 192.168.0.2:24800 and it still eventually timed out with error 9. > I have the Firewall disabled on both the client and the server. Can you ping 192.168.0.2 from the client? ..and nc -vz 192.168.0.2 24800 from the client?

No labels

Rows
Columns