github-starred/barrier

Fork 0

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

[GH-ISSUE #125] Mac OS X starting endlessly #99

New issue

Open

opened 2026-05-05 05:14:57 -06:00 by gitea-mirror · 10 comments

gitea-mirror commented

2026-05-05 05:14:57 -06:00

Owner

Originally created by @iwoj on GitHub (Sep 6, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/125

Operating Systems

Server: Mac OS X High Sierra

Client: Ubuntu 18

Barrier Version

2.1.0

Steps to reproduce bug

Setup Barrier as server
Click Start
Wait forever as it is stuck on "starting"

Other info

Does this bug prevent you from using Barrier entirely? Yes

Originally created by @iwoj on GitHub (Sep 6, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/125 ### Operating Systems ### Server: Mac OS X High Sierra Client: Ubuntu 18 ### Barrier Version ### 2.1.0 ### Steps to reproduce bug ### 1. Setup Barrier as server 2. Click Start 3. Wait forever as it is stuck on "starting" ### Other info ### * Does this bug prevent you from using Barrier entirely? Yes

gitea-mirror commented

2026-05-05 05:15:02 -06:00

Author

Owner

@OlivierChirouze commented on GitHub (Sep 6, 2018):

Same here

@OlivierChirouze commented on GitHub (Sep 6, 2018): Same here

gitea-mirror commented

2026-05-05 05:15:05 -06:00

Author

Owner

@OlivierChirouze commented on GitHub (Sep 6, 2018):

Apparently I fixed the issue by just naming the client screen... Now Barrier server is starting (I'm still not seeing the second screen, but at least the application starts)

@OlivierChirouze commented on GitHub (Sep 6, 2018): Apparently I fixed the issue by just **naming** the client screen... Now Barrier server is starting (I'm still not seeing the second screen, but at least the application starts)

gitea-mirror commented

2026-05-05 05:15:07 -06:00

Author

Owner

@OlivierChirouze commented on GitHub (Sep 6, 2018):

Ok I got it working! Brillant piece of software.
I was just struggling because I couldn't have the "top left" position working for the client screen: only left or top position are working...

@OlivierChirouze commented on GitHub (Sep 6, 2018): Ok I got it working! Brillant piece of software. I was just struggling because I couldn't have the "top left" position working for the client screen: only left or top position are working...

gitea-mirror commented

2026-05-05 05:15:09 -06:00

Author

Owner

@iwoj commented on GitHub (Sep 6, 2018):

This won't work for me. There's no client connected.

@iwoj commented on GitHub (Sep 6, 2018): This won't work for me. There's no client connected.

gitea-mirror commented

2026-05-05 05:15:12 -06:00

Author

Owner

@nielspeen commented on GitHub (Sep 7, 2018):

@iwoj what does your barrier log say?

I had the same issue as @OlivierChirouze and had to add the screens using the exact names mentioned in the log.

@nielspeen commented on GitHub (Sep 7, 2018): @iwoj what does your barrier log say? I had the same issue as @OlivierChirouze and had to add the screens using the exact names mentioned in the log.

gitea-mirror commented

2026-05-05 05:15:15 -06:00

Author

Owner

@walker0643 commented on GitHub (Sep 8, 2018):

I'll add that exact names are required. The name of the client must match the name given to the server config for that screen.

@walker0643 commented on GitHub (Sep 8, 2018): I'll add that exact names are required. The name of the client must match the name given to the server config for that screen.

gitea-mirror commented

2026-05-05 05:15:17 -06:00

Author

Owner

@OlivierChirouze commented on GitHub (Sep 10, 2018):

Sorry my reply was not complete:

on the client side I had to explicitly enter the IP of the server. I then opened logs, still on the server side, to verify that it was connected to server
on the server side when configuring the screen disposition I had to name the client screen just as it appears on the client side.

There doesn't seem to be an "auto detect" feature on the server, you have to explicitly add clients by their own names.

@OlivierChirouze commented on GitHub (Sep 10, 2018): Sorry my reply was not complete: - **on the client side** I had to explicitly enter the IP of the server. I then opened logs, still on the server side, to verify that it was connected to server - **on the server side** when configuring the screen disposition I had to name the client screen **just as it appears on the client side**. There doesn't seem to be an "auto detect" feature on the server, you have to explicitly add clients by their own names.

gitea-mirror commented

2026-05-05 05:15:20 -06:00

Author

Owner

@ghost commented on GitHub (Jan 20, 2019):

There is no information on where the config files are stored, and that information is not on anything related to Barrier on the internet.

Where is the default config file?

@ghost commented on GitHub (Jan 20, 2019): There is no information on where the config files are stored, and that information is not on anything related to Barrier on the internet. Where is the default config file?

gitea-mirror commented

2026-05-05 05:15:23 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Jan 20, 2019):

There is no default config file other than the settings in barrier -> change settings. The config files are generated as-needed during runtime for most unless you've specified a path to the config file.

@AdrianKoshka commented on GitHub (Jan 20, 2019): There is no default config file other than the settings in `barrier` -> `change settings`. The config files are generated as-needed during runtime for most unless you've specified a path to the config file.

gitea-mirror commented

2026-05-05 05:15:25 -06:00

Author

Owner

@paolocavagnolo commented on GitHub (Nov 13, 2020):

about the same configuration here:
barrier 2.3.3 - mac os high sierra as Server - ubuntu 20.04 as Client

same bug, solved by:
on Server, in configuration I add a new screen, named it as appear on the server barrier window, moved the two screen on the top left, one near the other

then it worked. thanks for the suggestion

@paolocavagnolo commented on GitHub (Nov 13, 2020): about the same configuration here: barrier 2.3.3 - mac os high sierra as **Server** - ubuntu 20.04 as **Client** same bug, solved by: on Server, in configuration I add a new screen, named it as appear on the server barrier window, **moved the two screen on the top left**, one near the other then it worked. thanks for the suggestion