search

debauchee / barrier

Open-source KVM software
Other
27.65k stars 1.52k forks source link

Mac OS X client 'forgets' server IP in manual config #143

Open thirdwheel opened 6 years ago

thirdwheel commented 6 years ago

Operating Systems

Server: Windows 10 Pro

Client: Mac OS X High Sierra

Barrier Version

2.1.0

Steps to reproduce bug

  1. On the client, untick 'Auto config' and set the server IP.
  2. Start Barrier and confirm that setting works.
  3. Restart Mac OS X.
  4. Open Barrier and see that the IP address is missing

Other info

AdrianKoshka commented 6 years ago

I was under the impression that this is how synergy(1.x)/barrier worked normally. Going to ping @debauchee/barrier-developers to confirm this.

BartmanEH commented 4 years ago

Using Windows 10 server and macOS 10.13.6 client v2.3.2 I have a similar issue except the client 'remembers' an old server IP address and I have to manually change it on every macOS startup. I cannot figure out a way to cause the client to connect automatically on startup to a specific server IP.

EDIT: I got the client to remember the server IP address by doing a purposeful Quit of the macOS Barrier client app (before shutting down). It seems that performing a Quit causes the client to 'remember' the server IP parameter.

jbreef commented 3 years ago

BartmanEH, thanks a bunch for this tip! I would never have figured this out. I have been struggling with Barrier remembering the old IP address of the server after a reboot of my iMac. This "feature" has been retained in v2.3.3 of Barrier. I have been struggling to locate the magic file and have deleted the app, the folder from ~/Library/Applications Support, even the Certificate without success. After seeing the EDIT to your post I brought up the Show window and reset the IP address and then quit the application. I restarted my iMac and to my surprise all the changes were retained and Barrier works perfectly. Thanks again.

micheal-icp commented 2 months ago

This isn't limited to MacOS cause it happens with Windows version too. Good news is, what BarmanEH mentioned about purposefully clicking "Quit" in the menu, triggers an actual save event.

This is definitely a bug in both Windows and MacOS versions (possibly other platforms), so this does need a fix. I would purpose performing the save action at the point the Barrier app is loaded after a change.