mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1057] Doesent work on a M1 .Mac #838
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#838
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 @user858753257 on GitHub (Feb 8, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1057
Describe the bug
A clear and concise description of what the bug is.
trying to connect from Linux mint 20 .
My MacBook doesent accept the connection . Firewall is off.
To Reproduce
Steps to reproduce the behavior:
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):
Barrier 2.3.3 on OSX 11.2
Barrier 2.3.2 on Linux mint 20.1 (remote)
Additional context
Add any other context about the problem here.
@adamwolf commented on GitHub (Feb 13, 2021):
Just a user here, but I was able to get my M1 mac to connect to a Barrier server. I did not try the other way around, with the M1 mac as the server.
@Celerii commented on GitHub (Feb 19, 2021):
I confirm that Barrier works well on my M1 MacBook Air (Big Sur 11.2.1) as a client, I did not see any problem.
@dafi commented on GitHub (Feb 19, 2021):
Server M1 (Big Sur)
Client Mac Mini 2012 (Catalina)
Client Mac Book Pro 2017 (Mojave)
Everything works fine
@unimatrix2 commented on GitHub (Feb 21, 2021):
Just tested on Mac to Mac and worked fine.
Server: iMac (Late 2012) - Catalina
Client: Mac Mini M1 - Big Sur
Worked right away. With the server started, opening the app on the M1 prompted the server to choose the display position and done. Mouse/keyboard & clipboard: awesome, drag n drop is a little sluggish to detect when the mouse reaches the border but works fine once you get the hang of it.
Btw I'm impressed, Synergy wouldn't work no matter what, and Barrier worked with only two clicks. Awesome work!
@kyserv commented on GitHub (Feb 22, 2021):
Hi - I am running into a strange issue on my M1 Mac mini running Big Sur as the Server.
When I launch the app on my Mac and attempt to start it seems to be stuck in some sort of loop where the app repeatedly keeps opening in the dock but never seems to open
Happy to answer questions or provide a log if needed. Maybe I'm just stuck on something stupid.
Yup - sorry to clarify looks like my issue is unrelated to the M1
[2021-02-21T23:52:50] INFO: starting server
[2021-02-21T23:52:50] INFO: config file: /private/var/folders/z2/nxg06nn96gq94sfv36k2zcbw0000gn/T/Barrier.mFuqdn
[2021-02-21T23:52:50] INFO: log level: INFO
[2021-02-21T23:52:50] INFO: drag and drop enabled
[2021-02-21T23:52:50] ERROR: cannot read configuration "/private/var/folders/z2/nxg06nn96gq94sfv36k2zcbw0000gn/T/Barrier.VTNWts": read error: line 18: duplicate screen name "COMPUTERNAME.local"
barriers: no configuration available
[2021-02-21T23:52:50] ERROR: process exited with error code: 4
[2021-02-21T23:52:50] INFO: detected process not running, auto restarting
@mcoolidge commented on GitHub (Feb 23, 2021):
I was having a similar issue. I would recommend you click the configure server button and remove all screens/devices and any hotkeys. The error seems to indicate the config file was corrupted or you added the same device twice.
If that doesn't fix it, you might want to save the configuration file and open it with a text editor to see if there are duplicate screens. Then remove the duplicates.
Hope this helps.
@tomhillmeyer commented on GitHub (Feb 24, 2021):
Thank you @mcoolidge! I was having the exactly same issue: server just wouldn't start on Big Sur. Removed all of the configured devices in the "configure server" screen and it booted right up. Cheers!
@kyserv commented on GitHub (Feb 24, 2021):
Thanks - just updating this thread that I was able to use your advice and got everything working correctly. I definitely had some bad or duplicate data in my setup and clearing everything out and starting fresh had it start working right away. Server working perfectly on my m1 Mac now
@diocletiann commented on GitHub (Apr 15, 2021):
Can we get a native build? This is how far I get (mac noob):
@tylerb153 commented on GitHub (Dec 17, 2021):
So I found having my M1 MacBook Air running macOS Monterey worked fine as a client running on Rosetta 2 but would run on a server. There’s a certificate that’s missing or something like that but it your able to install barrier on an intel Mac and steal its certificate it works perfectly fine so far. It’s in ~/Users/“user”/library/application support/barrier alternatively you can get the path from the log that the Mac will spit out as it tries and fails to start the server. It’s not a like perfect fix but it’s worked for me so far and maybe it will help you too until a native version is released
@rafaelatlucro commented on GitHub (Apr 11, 2022):
I was able to get this to work by stopping the server. Going to 'configure server', remove all the screens, drop in a random screen. Close the window. Run the 'server' first. Zero clue what combination of the above and macOS/app restarts led to this working but I have it working on two M1 macs running monterey. One computer refuses to be a client though, also not sure why. Just posting to see if this helps anyone
@jmahone commented on GitHub (Apr 11, 2022):
Did you ever see the issue I describe in #1530? I have an intel-based mbp
running Mojave (10.14.6) as the server, and my client machine is an M1 Pro
mbp running Monterey (12.1). I had previously gotten barrier 2.3.3 to work
on two intel-based mbps, where the server is the same one I just mentioned.
Now that I've changed the client machine, I just can't get it to work.
I've turned off SSL for now (though I had gotten that to work in that I was
able to generate the certs which seemed to quiet the SSL errors).
Here's a taste of what I'm seeing.
Currently, on the server (MBP 15” mid-2015, 10.14.6 Mojave, 2.8GHz Intel
Core i7), I get this message:
[2022-04-04T11:01:07] NOTE: accepted client connection
[2022-04-04T11:01:07] WARNING: a client with name "my-mbp" is already
connected
[2022-04-04T11:01:07] NOTE: disconnecting client "my-mbp"
[2022-04-04T11:01:07] NOTE: client "my-mbp" has disconnected
Currently, on the client (MBP 16” 2021, 12.1 Monterey, Apple M1 Pro), I get
this message:
T11:00:44] NOTE: connecting to '192.168.xx.yy': 192.168.xx.xxx:24800
[2022-04-04T11:00:44] ERROR: server already has a connected client with
name "my-mbp"
[2022-04-04T11:00:44] WARNING: failed to connect to server: server already
has a connected client with our name
Many thanks for any help you can provide,
Jerry
On Sun, Apr 10, 2022 at 9:51 PM rafaelatlucro @.***>
wrote:
@luis-henriquez-07 commented on GitHub (Apr 20, 2022):
I'm trying to client mac mini using a pc as a server but it doesn't work.
When client pc using mac mini as a server it works.
Can you help me?
@buermann commented on GitHub (Nov 8, 2022):
https://github.com/debauchee/barrier/issues/1609#issuecomment-1186281717