[GH-ISSUE #506] Stuck on Barrier is starting #396

New issue

Closed

opened 2026-05-05 06:16:33 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 06:16:33 -06:00

Owner

Originally created by @fieldengr2010 on GitHub (Nov 21, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/506

I'm attempting to use Barrier between a Debian 10 and macOS Catalina (10.15.1) but keep getting the Barrier is starting message.

The Debian box is configured as the server and is ready and waiting.

The Mac is configured as the client with the server IP entered, but it doesn't go past the "is starting" point.

Any potential ideas or pointers to where this might be coming from at all?

The same happens to the Mac if I make it the server.

Originally created by @fieldengr2010 on GitHub (Nov 21, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/506 I'm attempting to use Barrier between a Debian 10 and macOS Catalina (10.15.1) but keep getting the Barrier is starting message. The Debian box is configured as the server and is ready and waiting. The Mac is configured as the client with the server IP entered, but it doesn't go past the "is starting" point. Any potential ideas or pointers to where this might be coming from at all? The same happens to the Mac if I make it the server.

gitea-mirror

2026-05-05 06:16:33 -06:00

closed this issue
added the
macOS

bug

windows
labels

gitea-mirror commented

2026-05-05 06:16:38 -06:00

Author

Owner

@fieldengr2010 commented on GitHub (Nov 21, 2019):

Found the source of the problem. Turns out I hadn't put the screen name in correctly and so it was refusing to talk to the Linux box.

@fieldengr2010 commented on GitHub (Nov 21, 2019): Found the source of the problem. Turns out I hadn't put the screen name in correctly and so it was refusing to talk to the Linux box.

gitea-mirror commented

2026-05-05 06:16:39 -06:00

Author

Owner

@MisutaaAsriel commented on GitHub (Dec 8, 2022):

Found the source of the problem. Turns out I hadn't put the screen name in correctly and so it was refusing to talk to the Linux box.

Can I ask how you fixed this? I put in an invalid screen name by accident and now barrier just crashes in a loop.

I can't find any config files, and the generated config files have the correct screen name (but if you try launching barrier gui via the command line it shows that its being launched with "--name", "Invalid Name".

I'd love to change it but I can't get into the config panel.

It seems to be storing the data in some kind of shared store somewhere? And loading it that way. But I have no idea where that is at.

@MisutaaAsriel commented on GitHub (Dec 8, 2022): > Found the source of the problem. Turns out I hadn't put the screen name in correctly and so it was refusing to talk to the Linux box. Can I ask how you fixed this? I put in an invalid screen name by accident and now barrier just crashes in a loop. I can't find any config files, and the generated config files have the correct screen name (but if you try launching barrier gui via the command line it shows that its being launched with `"--name", "Invalid Name"`. I'd love to change it but I can't get into the config panel. It seems to be storing the data in some kind of shared store somewhere? And loading it that way. But I have no idea where that is at.

gitea-mirror referenced this issue

2026-05-05 07:57:58 -06:00

[PR #408] [MERGED] Fix memory leak during SSL socket shutdown #1626