All Activity

@ChrisC_1000Try after quitting all the application in the menu bar and all other running applications. Any one of it may prompt for password in background. It may cause the issue.

Second attempt with the -a option, the synergys process is up an running and the client connects to it. However I have the exact same issue, the keyboard doesn't switch focus to the client.

Does nothing for me, it quits right away (I'm using the same conf file as the GUI): $ /Applications/Synergy.app/Contents/MacOS/synergys -d DEBUG2 -c LastConfig.cfg [2021-06-17T09:57:56] DEBUG: opening configuration "LastConfig.cfg" [2021-06-17T09:57:56] DEBUG: configuration read successfully $

The second one option in my case for sure, as even rebooting won't help. It's ridiculous that this issue has been there for at least 4 years, probably more, across several releases and it hasn't been fixed yet.

A customer tested with 1.13 on Monterey and reported it worked without issues, but we haven't tested macOS 12 and Synergy 1.14 yet.

We explained more in our blog post here: https://symless.com/blog/putting-ux-first Our focus right now is improving Synergy 1, while also working on Synergy 3.

Obviously Monterey is a brandy new beta and I have no right to expect Synergy to work on it, and I have no problem with that - I was just wondering if anyone could share anecdotally if it worked for them if they installed the OS beta. Thanks!

Why was i asked to pay for Pro 2 for Symless to pull the plug on it? This Pro 1 is terrible and clunky to say the least, the Pro two seemed to just work with a simple login. It seems like a huge step back

We don't have any current plans to support Windows on ARM. The source code can be found here: https://github.com/symless/synergy-core

Helios, Still no answer here. Self-compiling isn't really an option: Synergy isn't open-source.

I bought Synergy when Synergy 2 was just released, and used it literally up untill today (I quite liked it for what I used it for, although there were some annoyances). So today I found out Synergy 2 was discontinued, and thus decided to download and replace Synergy 2 by Synergy 1. So I immediately ran into this issue, and had to go through the steps above to actually get it working again. Synergy 2 was so much easier to use already, so while this might get lost in the void, I just wanted to leave this thread on a positive note. If Syn2 was already such a step up, and it still wasnt

There are no plans to support iOS at this time.

@MikeBravo93 I would recommend contacting support for this: https://symless.com/contact-support

There are no current plans to support iOS

Hello, I encountered with the exactly same problem with @BennyLim, and I am eager to know about the method to fix it. I think it will be better to post here rather than sending emails for new users like me.

This feature would be so amazing with the new iPad Pros with M1 chip. Any updates on the possibility of synergy for iPadOS happening?

Damn I was looking for this. Such a shame.

Same problem for me. Mouse freeze on PC clients.

thank you!

While I can't offer much assistance on the Steamdeck hotkey config, I am sure separating the computers in the screens and links tab will disable edge detection

Hi! Just ran into this one myself. Any possibility of adding some better output at info level for this one? It's pretty cryptic right now: [2021-06-03T11:03:29] ERROR: cannot read configuration "C:/Users/marti/AppData/Local/Temp/Synergy.qitevy": read error: line 41: unknown screen name in switchToScreen synergys.exe: no configuration available [2021-06-03T11:03:30] ERROR: failed to launch, error: process immediately stopped [2021-06-03T11:03:30] INFO: backing off, wait=2s, failures=1 [2021-06-03T11:03:32] INFO: starting new process [2021-06-03T11:03:32] INFO: activeDesktop:Default

I have this exact problem. Takes about 2 mins for the cursor to re-appear on the server. Seemingly the server is hanging, when the cursor comes back the log adds about 6-8 entries containing "accepted client connection" then "new client disconnected". Massive pain, if anyone has a fix for this please let me know. It is embarrassing being on a video call and telling clients they have to wait 2 minutes while my mouse cursor reappears.

Well yeah I meant in actual functionality, I mentioned in the original post that I use a Stream Deck to run multiple hotkeys with one press that activates "lock the cursor to screen" every time I switch computers (F23 = "lock the cursor to screen", F13-15 = switch hosts): I could also see in the log that "lock the cursor to screen" was successfully activated whilst the issue continued to occur. I won't be able to test until later today, but I'll try splitting the PCs up via the grid and using the default lock hotkey.

Yes it is different. One is using the Scroll Lock key, and the other is setting a custom key. Scroll Lock is used for this function by default.

Thanks for the reply, is locking the cursor to the screen via Scroll Lock different than setting a custom hotkey for "lock the cursor to screen"? Guess I'll have to try separating the computers in the grid to see if that makes any difference.