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 #1364] Stuck on Barrier is Starting Mac OS #1062

New issue
Open
opened 2026-05-05 07:25:10 -06:00 by gitea-mirror · 16 comments
gitea-mirror commented 2026-05-05 07:25:10 -06:00
Owner
Copy link

Originally created by @Budoman on GitHub (Nov 2, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1364

What happened?

I downloaded and Installed the current build (2.4.0-release-3e0d758b) to my i9 iMac running Catalina 10.15.7 and my new MacBook Pro (16-inch, 2021) M1 Max running Monterey 12.0.1. I can launch and run either machine as a server and they recognize one another when other is set to client. However, when the server prompts me to choose position of the client, it opens the same prompt window twice and creates two client instances. Over on the client node, it stays in the state "Barrier is Starting" regardless of which machine is set as Server/Client.

Version

v2.3.3

Git commit hash (if applicable)

3e0d758b

If applicable, where did you install Barrier from?

download the .dmg from Github.

What OSes are you seeing the problem on? (Check all that apply)

macOS

What OS versions are you using?

Core i9 iMac (2020) running Catalina 10.15.7
new MacBook Pro (16-inch, 2021) M1 Max running Monterey 12.0.1

Relevant log output

No response

Any other information

No response

Originally created by @Budoman on GitHub (Nov 2, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1364 ### What happened? I downloaded and Installed the current build (2.4.0-release-3e0d758b) to my i9 iMac running Catalina 10.15.7 and my new MacBook Pro (16-inch, 2021) M1 Max running Monterey 12.0.1. I can launch and run either machine as a server and they recognize one another when other is set to client. However, when the server prompts me to choose position of the client, it opens the same prompt window twice and creates two client instances. Over on the client node, it stays in the state "Barrier is Starting" regardless of which machine is set as Server/Client. ### Version v2.3.3 ### Git commit hash (if applicable) 3e0d758b ### If applicable, where did you install Barrier from? download the .dmg from Github. ### What OSes are you seeing the problem on? (Check all that apply) macOS ### What OS versions are you using? Core i9 iMac (2020) running Catalina 10.15.7 new MacBook Pro (16-inch, 2021) M1 Max running Monterey 12.0.1 ### Relevant log output _No response_ ### Any other information _No response_
gitea-mirror added the
bug
 label 2026-05-05 07:25:10 -06:00
gitea-mirror commented 2026-05-05 07:25:13 -06:00
Author
Owner
Copy link

@mainTAP commented on GitHub (Nov 2, 2021):

I have a similar issue on High Sierra after upgrading from 2.3.3 :

[2021-11-02T09:34:22] INFO: config file: /private/var/folders/cp/210tpxmj1klfj_hkxypfv6gc0000gq/T/Barrier.xuKuyh
[2021-11-02T09:34:22] INFO: log level: INFO
[2021-11-02T09:34:22] INFO: drag and drop enabled
[2021-11-02T09:34:22] NOTE: started client
[2021-11-02T09:34:22] NOTE: connecting to '
[2021-11-02T09:34:22] INFO: OpenSSL 3.0.0 7 sep 2021
2021-11-02 09:34:22.423 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.439 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.439 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.439 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.439 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.442 barrierc[659:37793] starting cocoa loop
dyld: lazy symbol binding failed: Symbol not found: ____chkstk_darwin
  Referenced from: /Applications/Barrier.app/Contents/MacOS/barrierc
  Expected in: /usr/lib/libSystem.B.dylib
dyld: Symbol not found: ____chkstk_darwin
  Referenced from: /Applications/Barrier.app/Contents/MacOS/barrierc
  Expected in: /usr/lib/libSystem.B.dylib
[2021-11-02T09:34:22] ERROR: process exited with error code: 6
[2021-11-02T09:34:22] INFO: detected process not running, auto restarting
[2021-11-02T09:34:23] INFO: stopping barrier desktop process```

Ps: it looks like the same happens in 2.3.4
<!-- gh-comment-id:957307963 --> @mainTAP commented on GitHub (Nov 2, 2021): I have a similar issue on High Sierra after upgrading from 2.3.3 : ```[2021-11-02T09:34:22] INFO: starting client [2021-11-02T09:34:22] INFO: config file: /private/var/folders/cp/210tpxmj1klfj_hkxypfv6gc0000gq/T/Barrier.xuKuyh [2021-11-02T09:34:22] INFO: log level: INFO [2021-11-02T09:34:22] INFO: drag and drop enabled [2021-11-02T09:34:22] NOTE: started client [2021-11-02T09:34:22] NOTE: connecting to ' [2021-11-02T09:34:22] INFO: OpenSSL 3.0.0 7 sep 2021 2021-11-02 09:34:22.423 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.439 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.439 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.439 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.439 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! 2021-11-02 09:34:22.442 barrierc[659:37793] starting cocoa loop dyld: lazy symbol binding failed: Symbol not found: ____chkstk_darwin Referenced from: /Applications/Barrier.app/Contents/MacOS/barrierc Expected in: /usr/lib/libSystem.B.dylib dyld: Symbol not found: ____chkstk_darwin Referenced from: /Applications/Barrier.app/Contents/MacOS/barrierc Expected in: /usr/lib/libSystem.B.dylib [2021-11-02T09:34:22] ERROR: process exited with error code: 6 [2021-11-02T09:34:22] INFO: detected process not running, auto restarting [2021-11-02T09:34:23] INFO: stopping barrier desktop process``` Ps: it looks like the same happens in 2.3.4
gitea-mirror commented 2026-05-05 07:25:14 -06:00
Author
Owner
Copy link

@p12tic commented on GitHub (Nov 2, 2021):

@mainTAP Just to confirm, 2.3.3 works, 2.3.4 doesn't, right?

<!-- gh-comment-id:957339906 --> @p12tic commented on GitHub (Nov 2, 2021): @mainTAP Just to confirm, 2.3.3 works, 2.3.4 doesn't, right?
gitea-mirror commented 2026-05-05 07:25:15 -06:00
Author
Owner
Copy link

@mainTAP commented on GitHub (Nov 2, 2021):

@mainTAP Just to confirm, 2.3.3 works, 2.3.4 doesn't, right?

Yes, going back to 2.3.3 works

<!-- gh-comment-id:957346712 --> @mainTAP commented on GitHub (Nov 2, 2021): > @mainTAP Just to confirm, 2.3.3 works, 2.3.4 doesn't, right? Yes, going back to 2.3.3 works
gitea-mirror commented 2026-05-05 07:25:16 -06:00
Author
Owner
Copy link

@shymega commented on GitHub (Nov 2, 2021):

OK, this is probably related to the CI builds included in the release notes.

The link is below - it's from a CI build of 2.4.0.

https://dev.azure.com/debauchee/Barrier/_build/results?buildId=618&view=artifacts&pathAsName=false&type=publishedArtifacts

You should be able to see the page, I don't think it's protected, but there are separate builds for different macOS versions. The 'symbol not found' would indicate a linking issue on a newer/older macOS version.

And the link below is from a CI build of 2.3.4:

https://dev.azure.com/debauchee/Barrier/_build/results?buildId=617&view=artifacts&pathAsName=false&type=publishedArtifacts

So, my suggestion is to attempt using one artefact from either link that matches your macOS version - and let me know, if that's the case, we can update the release on GitHub.

Thanks =)

On Tue, Nov 2, 2021, at 11:19 AM, mainTAP wrote:

@mainTAP https://github.com/mainTAP Just to confirm, 2.3.3 works, 2.3.4 doesn't, right?

Yes, going back to 2.3.3 works

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/debauchee/barrier/issues/1364#issuecomment-957346712,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKF2QHIE5T2GNBAGLTGAI3UJ7CLFANCNFSM5HFRTZFA.

--
Kind regards,

Dom Rodriguez (also known as shymega)

<!-- gh-comment-id:957874222 --> @shymega commented on GitHub (Nov 2, 2021): OK, this is probably related to the CI builds included in the release notes. The link is below - it's from a CI build of 2.4.0. https://dev.azure.com/debauchee/Barrier/_build/results?buildId=618&view=artifacts&pathAsName=false&type=publishedArtifacts You should be able to see the page, I don't think it's protected, but there are separate builds for different macOS versions. The 'symbol not found' would indicate a linking issue on a newer/older macOS version. And the link below is from a CI build of 2.3.4: https://dev.azure.com/debauchee/Barrier/_build/results?buildId=617&view=artifacts&pathAsName=false&type=publishedArtifacts So, my suggestion is to attempt using one artefact from either link that matches your macOS version - and let me know, if that's the case, we can update the release on GitHub. Thanks =) On Tue, Nov 2, 2021, at 11:19 AM, mainTAP wrote: >> @mainTAP <https://github.com/mainTAP> Just to confirm, 2.3.3 works, 2.3.4 doesn't, right? >> > Yes, going back to 2.3.3 works > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/debauchee/barrier/issues/1364#issuecomment-957346712>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAKF2QHIE5T2GNBAGLTGAI3UJ7CLFANCNFSM5HFRTZFA>. -- Kind regards, -- Dom Rodriguez (also known as shymega)
gitea-mirror commented 2026-05-05 07:25:16 -06:00
Author
Owner
Copy link

@p12tic commented on GitHub (Nov 2, 2021):

Indeed, the issue is obvious. I've just deleted a comment asking the user to do bisection.

<!-- gh-comment-id:957875674 --> @p12tic commented on GitHub (Nov 2, 2021): Indeed, the issue is obvious. I've just deleted a comment asking the user to do bisection.
gitea-mirror commented 2026-05-05 07:25:18 -06:00
Author
Owner
Copy link

@p12tic commented on GitHub (Nov 2, 2021):

Reformatting the logs should have been the first thing I do.

<!-- gh-comment-id:957876000 --> @p12tic commented on GitHub (Nov 2, 2021): Reformatting the logs should have been the first thing I do.
gitea-mirror commented 2026-05-05 07:25:18 -06:00
Author
Owner
Copy link

@mainTAP commented on GitHub (Nov 2, 2021):

OK, this is probably related to the CI builds included in the release notes. The link is below - it's from a CI build of 2.4.0. https://dev.azure.com/debauchee/Barrier/_build/results?buildId=618&view=artifacts&pathAsName=false&type=publishedArtifacts You should be able to see the page, I don't think it's protected, but there are separate builds for different macOS versions. The 'symbol not found' would indicate a linking issue on a newer/older macOS version. And the link below is from a CI build of 2.3.4: https://dev.azure.com/debauchee/Barrier/_build/results?buildId=617&view=artifacts&pathAsName=false&type=publishedArtifacts So, my suggestion is to attempt using one artefact from either link that matches your macOS version - and let me know, if that's the case, we can update the release on GitHub. Thanks =)

Thank you, I'm running macOS 10.13.6 but the one from 10.14 worked

<!-- gh-comment-id:957910998 --> @mainTAP commented on GitHub (Nov 2, 2021): > OK, this is probably related to the CI builds included in the release notes. The link is below - it's from a CI build of 2.4.0. https://dev.azure.com/debauchee/Barrier/_build/results?buildId=618&view=artifacts&pathAsName=false&type=publishedArtifacts You should be able to see the page, I don't think it's protected, but there are separate builds for different macOS versions. The 'symbol not found' would indicate a linking issue on a newer/older macOS version. And the link below is from a CI build of 2.3.4: https://dev.azure.com/debauchee/Barrier/_build/results?buildId=617&view=artifacts&pathAsName=false&type=publishedArtifacts So, my suggestion is to attempt using one artefact from either link that matches your macOS version - and let me know, if that's the case, we can update the release on GitHub. Thanks =) Thank you, I'm running macOS 10.13.6 but the one from 10.14 worked
gitea-mirror commented 2026-05-05 07:25:19 -06:00
Author
Owner
Copy link

@shymega commented on GitHub (Nov 3, 2021):

Righto. Azure doesn't support macOS 10.13 build agents, but if macOS 10.14 works for you - that's great!

On Tue, Nov 2, 2021, at 4:20 PM, mainTAP wrote:

OK, this is probably related to the CI builds included in the release notes. The link is below - it's from a CI build of 2.4.0. https://dev.azure.com/debauchee/Barrier/_build/results?buildId=618&view=artifacts&pathAsName=false&type=publishedArtifacts You should be able to see the page, I don't think it's protected, but there are separate builds for different macOS versions. The 'symbol not found' would indicate a linking issue on a newer/older macOS version. And the link below is from a CI build of 2.3.4: https://dev.azure.com/debauchee/Barrier/_build/results?buildId=617&view=artifacts&pathAsName=false&type=publishedArtifacts So, my suggestion is to attempt using one artefact from either link that matches your macOS version - and let me know, if that's the case, we can update the release on GitHub. Thanks =)

Thank you, I'm running macOS 10.13.6 but the one from 10.14 worked

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/debauchee/barrier/issues/1364#issuecomment-957910998,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKF2QAZUWJVAMHJXPDQMOTUKAFVLANCNFSM5HFRTZFA.

--
Kind regards,

Dom Rodriguez (also known as shymega)

<!-- gh-comment-id:959118036 --> @shymega commented on GitHub (Nov 3, 2021): Righto. Azure doesn't support macOS 10.13 build agents, but if macOS 10.14 works for you - that's great! On Tue, Nov 2, 2021, at 4:20 PM, mainTAP wrote: >> OK, this is probably related to the CI builds included in the release notes. The link is below - it's from a CI build of 2.4.0. https://dev.azure.com/debauchee/Barrier/_build/results?buildId=618&view=artifacts&pathAsName=false&type=publishedArtifacts You should be able to see the page, I don't think it's protected, but there are separate builds for different macOS versions. The 'symbol not found' would indicate a linking issue on a newer/older macOS version. And the link below is from a CI build of 2.3.4: https://dev.azure.com/debauchee/Barrier/_build/results?buildId=617&view=artifacts&pathAsName=false&type=publishedArtifacts So, my suggestion is to attempt using one artefact from either link that matches your macOS version - and let me know, if that's the case, we can update the release on GitHub. Thanks =) >> > Thank you, I'm running macOS 10.13.6 but the one from 10.14 worked > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/debauchee/barrier/issues/1364#issuecomment-957910998>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAKF2QAZUWJVAMHJXPDQMOTUKAFVLANCNFSM5HFRTZFA>. -- Kind regards, -- Dom Rodriguez (also known as shymega)
gitea-mirror commented 2026-05-05 07:25:21 -06:00
Author
Owner
Copy link

@fakezeta commented on GitHub (Nov 10, 2021):

Righto. Azure doesn't support macOS 10.13 build agents, but if macOS 10.14 works for you - that's great!
…
On Tue, Nov 2, 2021, at 4:20 PM, mainTAP wrote: > OK, this is probably related to the CI builds included in the release notes. The link is below - it's from a CI build of 2.4.0. https://dev.azure.com/debauchee/Barrier/_build/results?buildId=618&view=artifacts&pathAsName=false&type=publishedArtifacts You should be able to see the page, I don't think it's protected, but there are separate builds for different macOS versions. The 'symbol not found' would indicate a linking issue on a newer/older macOS version. And the link below is from a CI build of 2.3.4: https://dev.azure.com/debauchee/Barrier/_build/results?buildId=617&view=artifacts&pathAsName=false&type=publishedArtifacts So, my suggestion is to attempt using one artefact from either link that matches your macOS version - and let me know, if that's the case, we can update the release on GitHub. Thanks =) > Thank you, I'm running macOS 10.13.6 but the one from 10.14 worked — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1364 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKF2QAZUWJVAMHJXPDQMOTUKAFVLANCNFSM5HFRTZFA.
-- Kind regards, -- Dom Rodriguez (also known as shymega)

Just to confirm the same issue with 2.4.0 on macOS 10.13.6. Solved with 10.14 artifact.

Thank you

<!-- gh-comment-id:965750159 --> @fakezeta commented on GitHub (Nov 10, 2021): > Righto. Azure doesn't support macOS 10.13 build agents, but if macOS 10.14 works for you - that's great! > […](#) > On Tue, Nov 2, 2021, at 4:20 PM, mainTAP wrote: > OK, this is probably related to the CI builds included in the release notes. The link is below - it's from a CI build of 2.4.0. https://dev.azure.com/debauchee/Barrier/_build/results?buildId=618&view=artifacts&pathAsName=false&type=publishedArtifacts You should be able to see the page, I don't think it's protected, but there are separate builds for different macOS versions. The 'symbol not found' would indicate a linking issue on a newer/older macOS version. And the link below is from a CI build of 2.3.4: https://dev.azure.com/debauchee/Barrier/_build/results?buildId=617&view=artifacts&pathAsName=false&type=publishedArtifacts So, my suggestion is to attempt using one artefact from either link that matches your macOS version - and let me know, if that's the case, we can update the release on GitHub. Thanks =) > Thank you, I'm running macOS 10.13.6 but the one from 10.14 worked — You are receiving this because you commented. Reply to this email directly, view it on GitHub <[#1364 (comment)](https://github.com/debauchee/barrier/issues/1364#issuecomment-957910998)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKF2QAZUWJVAMHJXPDQMOTUKAFVLANCNFSM5HFRTZFA>. > -- Kind regards, -- Dom Rodriguez (also known as shymega) Just to confirm the same issue with 2.4.0 on macOS 10.13.6. Solved with 10.14 artifact. Thank you
gitea-mirror commented 2026-05-05 07:25:22 -06:00
Author
Owner
Copy link

@sderose commented on GitHub (Dec 10, 2021):

I just installed 2.4.0-release on a MacBook Pro running Big Sur (11.6) with a 4K external monitor, and a client MacBook Air M1 running 11.6.1. When I try to start them up, both get stuck at "Barrier is starting". Have tried autoconfig and giving the client the server's IP address; no difference.

<!-- gh-comment-id:991321894 --> @sderose commented on GitHub (Dec 10, 2021): I just installed 2.4.0-release on a MacBook Pro running Big Sur (11.6) with a 4K external monitor, and a client MacBook Air M1 running 11.6.1. When I try to start them up, both get stuck at "Barrier is starting". Have tried autoconfig and giving the client the server's IP address; no difference.
gitea-mirror commented 2026-05-05 07:25:24 -06:00
Author
Owner
Copy link

@klutzak commented on GitHub (Dec 21, 2021):

I just installed 2.4.0-release on a MacBook Pro running Big Sur (11.6) with a 4K external monitor, and a client MacBook Air M1 running 11.6.1. When I try to start them up, both get stuck at "Barrier is starting". Have tried autoconfig and giving the client the server's IP address; no difference.

I have the same issue; running the server on a Win11 PC and the client on a MacBook Pro M1 - MacOS 12.1.
Windows server autodetects and allows me to select the Mac client - but the Mac client is stuck on 'starting'.

<!-- gh-comment-id:998913224 --> @klutzak commented on GitHub (Dec 21, 2021): > I just installed 2.4.0-release on a MacBook Pro running Big Sur (11.6) with a 4K external monitor, and a client MacBook Air M1 running 11.6.1. When I try to start them up, both get stuck at "Barrier is starting". Have tried autoconfig and giving the client the server's IP address; no difference. I have the same issue; running the server on a Win11 PC and the client on a MacBook Pro M1 - MacOS 12.1. Windows server autodetects and allows me to select the Mac client - but the Mac client is stuck on 'starting'.
gitea-mirror commented 2026-05-05 07:25:25 -06:00
Author
Owner
Copy link

@robolmos commented on GitHub (Jan 12, 2022):

The CI links are blank for me. Is the 10.14 artifact able to be linked to the appropriate github releases please?

Also using 10.13.6 for one of the computers. 2.3.3 works, 2.3.4 and 2.4.0 do not, haven't tried the 10.14 artifact yet. Looks like Azure is removing the 10.14 image in the near future.

<!-- gh-comment-id:1011544174 --> @robolmos commented on GitHub (Jan 12, 2022): The CI links are blank for me. Is the 10.14 artifact able to be linked to the appropriate github releases please? Also using 10.13.6 for one of the computers. 2.3.3 works, 2.3.4 and 2.4.0 do not, haven't tried the 10.14 artifact yet. Looks like Azure is removing the 10.14 image in the near future.
gitea-mirror commented 2026-05-05 07:25:26 -06:00
Author
Owner
Copy link

@shymega commented on GitHub (Jan 13, 2022):

I'm no longer involved in the Barrier project, and I no longer have access to the CI infrastructure.

<!-- gh-comment-id:1012480300 --> @shymega commented on GitHub (Jan 13, 2022): I'm no longer involved in the Barrier project, and I no longer have access to the CI infrastructure.
gitea-mirror commented 2026-05-05 07:25:27 -06:00
Author
Owner
Copy link

@PeterIPROOV commented on GitHub (Feb 16, 2022):

I am having the same issues, is there an easy step-by-step to sort this?

<!-- gh-comment-id:1042331936 --> @PeterIPROOV commented on GitHub (Feb 16, 2022): I am having the same issues, is there an easy step-by-step to sort this?
gitea-mirror commented 2026-05-05 07:25:28 -06:00
Author
Owner
Copy link

@alexmill commented on GitHub (Oct 10, 2022):

Running this set of commands on both of my machines seems to resolve this issue for me:

cd  /Users/username/Library/Application\ Support/barrier/SSL/
mkdir -p Fingerprints
openssl req -x509 -nodes -days 365 -subj /CN=barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem
openssl x509 -fingerprint -sha1 -noout -in Barrier.pem > Fingerprints/Local.txt
sed -e "s/.*=//" Fingerprints/Local.txt

From this SO answer: https://stackoverflow.com/a/67343805/2628402

<!-- gh-comment-id:1273604387 --> @alexmill commented on GitHub (Oct 10, 2022): Running this set of commands on both of my machines seems to resolve this issue for me: ```bash cd /Users/username/Library/Application\ Support/barrier/SSL/ mkdir -p Fingerprints openssl req -x509 -nodes -days 365 -subj /CN=barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem openssl x509 -fingerprint -sha1 -noout -in Barrier.pem > Fingerprints/Local.txt sed -e "s/.*=//" Fingerprints/Local.txt ``` From this SO answer: https://stackoverflow.com/a/67343805/2628402
gitea-mirror commented 2026-05-05 07:25:31 -06:00
Author
Owner
Copy link

@frogcrush commented on GitHub (Jun 5, 2024):

In my case, turning off SSL on both the client and server resolved my issue.

<!-- gh-comment-id:2150881854 --> @frogcrush commented on GitHub (Jun 5, 2024): In my case, turning off SSL on both the client and server resolved my issue.
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#1062
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?