Imported issue:
Steps to reproduce:
Config:
section options:
keystroke(super+a) = switchToScreen(OSX)
keystroke(super+b) = switchToScreen(Windows)
Expected Result:
Option+A should move the cursor and focus to the OSX Server
Option+B should move the cursor and focus to the Windows Client
Actual Result:
Option+A moves the cursor and focus to the OSX Server
Option+B does nothing.
Notes:
To follow up.
F16 only locks/unlocks if I'm on one of the client machines, it will not lock if I'm focused on the server.
Ctrl+F15 and Shift+F15 _only_ works if I am focused on either client, but will not work if I'm focused on the server.
In other words, if I lock cursor, then F15 back to Server, I can no longer use F16 to unlock, or Ctrl/Shift + F15 to get back to one of the clients, I just shutdown the server and restart it in order to get cursor back to one of the clients.
Debug Log (Keystrokes F16, F15, Shift+F15, Ctrl+F15 add nothing to the log when screen is focused on the server).
> NOTE: starting server NOTE: command:
> /Applications/Synergy.app/Contents/MacOS/synergys -f --no-tray --debug
> DEBUG --name KBMac --crypto-pass b604ce8b33fc9100b215d38383a1678a
> --enable-drag-drop --log /private/var/log/synergy.log -c /Users/kbeezie/synergy.conf --address :24800 NOTE: config file:
> /Users/kbeezie/synergy.conf NOTE: log level: DEBUG NOTE: log file:
> /private/var/log/synergy.log INFO: Synergy 1.4.14 Server on Darwin
> 11.4.2 Darwin Kernel Version 11.4.2: Thu Aug 23 16:26:45 PDT 2012; root:xnu-1699.32.7~1/RELEASE_I386 i386 INFO: drag and drop enabled
> DEBUG: opening configuration "/Users/kbeezie/synergy.conf" DEBUG:
> configuration read successfully DEBUG: screen shape: center=0,0
> size=1280x800 on 1 display DEBUG: starting watchSystemPowerThread
> DEBUG: adopting new buffer DEBUG: discarding 1 event(s) DEBUG: opened
> display DEBUG: started watchSystemPowerThread DEBUG: registered hotkey
> F15 (id=efcc mask=0000) as id=1 DEBUG: registered hotkey Shift+F15
> (id=efcc mask=0001) as id=2 DEBUG: registered hotkey Control+F15
> (id=efcc mask=0002) as id=3 DEBUG: registered hotkey F16 (id=efcd
> mask=0000) as id=4 DEBUG: registered hotkey F13 (id=efca mask=0000) as
> id=5 DEBUG: registered hotkey Shift+F10 (id=efc7 mask=0001) as id=6
> DEBUG: registered hotkey Shift+F11 (id=efc8 mask=0001) as id=7 DEBUG:
> registered hotkey Shift+F12 (id=efc9 mask=0001) as id=8 DEBUG:
> registered hotkey Control+KP_Equal (id=efbd mask=0002) as id=9 DEBUG:
> registered hotkey Control+KP_Divide (id=efaf mask=0002) as id=10
> DEBUG: registered hotkey Control+KP_Multiply (id=efaa mask=0002) as
> id=11 NOTE: started server, waiting for clients NOTE: accepted client
> connection INFO: crypto mode: cfb DEBUG: received client "KBeezie-DPC"
> info shape=0,0 1280x1024 at -18624,0 NOTE: client "desk" has connected
> NOTE: accepted client connection INFO: crypto mode: cfb DEBUG:
> received client "Karl-HP" info shape=0,0 1280x1024 at -25792,0 NOTE:
> client "win" has connected DEBUG: starting carbon loop 2013-10-20
> 20:17:50.937 synergys[41128:507] starting cocoa loop INFO: switch from
> "mac" to "desk" at 0,593 INFO: leaving screen DEBUG: hiding cursor
> DEBUG: opening clipboard DEBUG: closing clipboard DEBUG: ignored
> screen "mac" update of clipboard 0 (unchanged) DEBUG: opening
> clipboard DEBUG: closing clipboard DEBUG: ignored screen "mac" update
> of clipboard 1 (unchanged) DEBUG: send clipboard 0 to "KBeezie-DPC"
> size=4 DEBUG: send clipboard 1 to "KBeezie-DPC" size=4 INFO: switch
> from "desk" to "win" at 2,699 DEBUG: send clipboard 0 to "Karl-HP"
> size=4 DEBUG: send clipboard 1 to "Karl-HP" size=4 DEBUG: cursor
> locked to current screen INFO: switch from "win" to "desk" at 640,512
> INFO: switch from "desk" to "win" at 189,730 DEBUG: cursor unlocked
> from current screen INFO: switch from "win" to "desk" at 1278,444
> INFO: switch from "desk" to "mac" at 1275,419 INFO: entering screen
> DEBUG: showing cursor INFO: switch from "mac" to "desk" at 0,556 INFO:
> leaving screen DEBUG: hiding cursor DEBUG: opening clipboard DEBUG:
> closing clipboard DEBUG: ignored screen "mac" update of clipboard 0
> (unchanged) DEBUG: opening clipboard DEBUG: closing clipboard DEBUG:
> ignored screen "mac" update of clipboard 1 (unchanged) INFO: switch
> from "desk" to "mac" at 1278,491 INFO: entering screen DEBUG: showing
> cursor INFO: switch from "mac" to "desk" at 0,638 INFO: leaving screen
> DEBUG: hiding cursor DEBUG: opening clipboard DEBUG: closing clipboard
> DEBUG: ignored screen "mac" update of clipboard 0 (unchanged) DEBUG:
> opening clipboard DEBUG: closing clipboard DEBUG: ignored screen "mac"
> update of clipboard 1 (unchanged) DEBUG: cursor locked to current
> screen INFO: switch from "desk" to "win" at 189,730 INFO: switch from
> "win" to "desk" at 241,616 INFO: switch from "desk" to "mac" at
> 943,635 INFO: entering screen DEBUG: showing cursor DEBUG: locked to
> screen DEBUG: locked to screen DEBUG: locked to screen DEBUG: locked
> to screen DEBUG: locked to screen DEBUG: locked to screen DEBUG:
> locked to screen DEBUG: locked to screen DEBUG: locked to screen
> DEBUG: locked to screen DEBUG: locked to screen DEBUG: locked to
> screen NOTE: stopping synergy desktop process
It seems like on the mac, the control key is only seen as meta, but when the cursor is over on the windows side the control key is seen as control. It's very confusing and wasn't doing this before.
To add even more confusion.
I set the following
F13 = switch to mac [server - osx 10.7]
F14 = switch to desk [client - Win7]
F15 = switch to win [client - Win8.1]
F16 = lock cursor [toggle]
The debug log while on either client shows that I'm pressing F14 thru F16. But if I'm currently focused on the server none of those keys do anything at all. They only behave when I'm focused on one of the clients. Which leads to a problem, if I F14, I can't unlock the cursor and I can't get back to the clients without restarting synergy.
I've tried a ton of other keyboard combinations and none of them are reacting when I'm currently on the server, only if my cursor is on a client.
Problem persists with 1.4.15
I've downgraded both server and clients back down to 1.4.12 where the config is working normally without problems since neither 1.4.14 nor 1.4.15 will work the way it's supposed to.
I am about to rip it asunder, so for the record, here is the original description:
Installed 1.4.14 (w/ encryption and signed in as Premium) on:
OSX 10.7 (Server)
Windows 7 Ultimate SP1 (Client)
Windows 8.1 Pro (Client)
The following options in my synergy config (was working previously with 1.4.12)
section: options
relativeMouseMoves = true
screenSaverSync = false
keystroke(F15) = switchToScreen(mac)
keystroke(shift+F15) = switchToScreen(desk)
keystroke(control+F15) = switchToScreen(win)
keystroke(F16) = lockCursorToScreen(toggle)
keystroke(F13) = keystroke(Print,desk)
keystroke(shift+F10) = keystroke(F10,desk)
keystroke(shift+F11) = keystroke(F11,desk)
keystroke(shift+F12) = keystroke(F12,desk)
keystroke(control+KP_Equal) = keystroke(AudioMute,win)
keystroke(control+KP_Divide) = keystroke(AudioDown,win)
keystroke(control+KP_Multiply) = keystroke(AudioUp,win)
end
While F15 does send the control back to the main OSX server, Shift+F15 or Ctrl+F15 are non-responsive.
Likewise Ctrl+KP_EQUAL, KP_DIVID, and KP_Multilply are no longer responsive.
F16 will lock the cursor to the screen, but won't unlock it sometimes when pressing F16 again (ie: I have to tap it several times to make it unlock).
As far as I can tell every other keystroke in options works (those not using a modifier in front).
Expecting it to perform the defined actions above as it did in 1.4.12
I'm experiencing this same issue with Mac OS 10.9.2 client and server - keystroke() entries in the options section work when the keystroke is performed when the synergy client is the active screen, but not when the synergy server is the active screen. The issue is still present in 1.4.18-r2096. Here's my snipped debug log showing the F5 (keycode 96) and F6 (keycode 97) events triggering switchToScreen() when focus is on the client, but not when the focus is on the server:
DEBUG: registered hotkey F5 (id=efc2 mask=0000) as id=1
DEBUG: registered hotkey F6 (id=efc3 mask=0000) as id=2
DEBUG: could not map hotkey id=ef14 mask=0000
DEBUG1: mask: 0000
DEBUG1: registered event type disconnected as 34
DEBUG1: registered event type screenSwitched as 35
NOTE: started server, waiting for clients
DEBUG1: registered event type reloadConfig as 36
DEBUG1: registered event type forceReconnect as 37
DEBUG1: registered event type resetServer as 38
DEBUG1: thread 0x00000004 entry
NOTE: accepted client connection
INFO: crypto mode: cfb
DEBUG1: registered event type inputReady as 39
DEBUG1: registered event type outputError as 40
DEBUG1: registered event type inputShutdown as 41
DEBUG1: registered event type outputShutdown as 42
DEBUG1: saying hello
DEBUG1: registered event type success as 43
DEBUG1: registered event type failure as 44
DEBUG1: registered event type outputFlushed as 45
DEBUG1: parsing hello reply
DEBUG1: querying client "node164.cit.geneseo.edu" info
DEBUG1: created proxy for client "node164.cit.geneseo.edu" version 1.5
DEBUG1: registered event type ready as 46
DEBUG1: registered event type disconnected as 47
DEBUG: received client "node164.cit.geneseo.edu" info shape=0,-264 4240x1440 at 4016,613
DEBUG1: send info ack to "node164.cit.geneseo.edu"
NOTE: client "node164.cit.geneseo.edu" has connected
DEBUG1: send reset options to "node164.cit.geneseo.edu"
DEBUG1: send set options to "node164.cit.geneseo.edu" size=22
DEBUG: starting carbon loop
DEBUG1: event: Key event kind: 10, keycode=96
DEBUG1: new mask: 0x0000
DEBUG1: onKeyDown id=61378 mask=0x0000 button=0x0061
DEBUG1: event: Key event kind: 11, keycode=96
DEBUG1: new mask: 0x0000
DEBUG1: onKeyUp id=0 mask=0x0000 button=0x0061
DEBUG1: event: Key event kind: 10, keycode=97
DEBUG1: new mask: 0x0000
DEBUG1: onKeyDown id=61379 mask=0x0000 button=0x0062
DEBUG1: event: Key event kind: 11, keycode=97
DEBUG1: new mask: 0x0000
DEBUG1: onKeyUp id=0 mask=0x0000 button=0x0062
DEBUG1: try to leave "node69.cit.geneseo.edu" on left
DEBUG1: mask: 0000
INFO: switch from "node69.cit.geneseo.edu" to "node164.cit.geneseo.edu" at 4239,659
INFO: leaving screen
DEBUG: hiding cursor
WARNING: cursor may not be visible
DEBUG1: mask: 0000
DEBUG1: modifiers on update: 0x0000
DEBUG: opening clipboard
DEBUG: closing clipboard
INFO: screen "node69.cit.geneseo.edu" updated clipboard 0
DEBUG: opening clipboard
DEBUG: closing clipboard
INFO: screen "node69.cit.geneseo.edu" updated clipboard 1
DEBUG1: mask: 0000
DEBUG1: send enter to "node164.cit.geneseo.edu", 4239,659 1 0000
DEBUG: send clipboard 0 to "node164.cit.geneseo.edu" size=61
DEBUG: send clipboard 1 to "node164.cit.geneseo.edu" size=61
DEBUG1: event: Key event kind: 10, keycode=96
DEBUG1: activate actions
DEBUG1: hotkey: switchToScreen(node164.cit.geneseo.edu)
INFO: switch from "node164.cit.geneseo.edu" to "node164.cit.geneseo.edu" at 3804,665
DEBUG1: event: Key event kind: 11, keycode=96
DEBUG1: deactivate actions
DEBUG1: event: Key event kind: 10, keycode=97
DEBUG1: activate actions
DEBUG1: hotkey: switchToScreen(node69.cit.geneseo.edu)
INFO: switch from "node164.cit.geneseo.edu" to "node69.cit.geneseo.edu" at 979,1237
DEBUG1: send leave to "node164.cit.geneseo.edu"
DEBUG1: mask: 0000
INFO: entering screen
DEBUG: showing cursor
lock cursor to screen doesn't work either when the screen is on the OS X Server.
^ Using 1.4.17
A user emailed in a patch which worked for his particular setup:
--- src/lib/platform/OSXScreen.cpp.orig 2014-06-30 10:10:16.000000000 -0300
+++ src/lib/platform/OSXScreen.cpp 2014-06-30 10:10:33.000000000 -0300
@@ -1345,7 +1345,7 @@
// all hotkeys so we can capture the OS defined hot keys as regular
// keystrokes but that means we don't get our own hot keys either.
// so we check for a key/modifier match in our hot key map.
trying again:
A user emailed in a patch which worked for his particular setup:--- src/lib/platform/OSXScreen.cpp.orig 2014-06-30 10:10:16.000000000 -0300
+++ src/lib/platform/OSXScreen.cpp 2014-06-30 10:10:33.000000000 -0300
@@ -1345,7 +1345,7 @@
// all hotkeys so we can capture the OS defined hot keys as regular
// keystrokes but that means we don't get our own hot keys either.
// so we check for a key/modifier match in our hot key map.
This issue is not limited to switchToScreen hotkeys, most (or all) hotkeys on a Mac server do not work when the focus is on the Mac server. If the focus is on the client, the hotkeys then work. This was broken in Synergy 1.4.14. It last worked well in Synergy 1.4.12.
Happy to find out this is being worked on.
Running Synergy on OS X 10.8 and the hotkey functionality appears to be completely non-functional.
:+1: same thing here OSX 10.9.5, Synergy 1.7.3.
Same issue, OSX 10.8.5 server 1.7.4 (Nightly Build) , Ubuntu 15.0.5 Client .
Now here is something interesting , that if I set the hotkey to a mousebutton it works on OSX.
I think the problem is with the OSX keyboard shortcuts setting, the OS ignores them or executes them differently maybe.
:+1: same thing here, just spent awhile troubleshooting before turning to Google and finding this issue. Using Synergy Pro v1.7.4 on OS X 10.11
If Anyone wants a kind of temporary fix here is a .conf that works
section: screens
Mac:
halfDuplexCapsLock = false
halfDuplexNumLock = false
halfDuplexScrollLock = false
xtestIsXineramaUnaware = false
switchCorners = none
switchCornerSize = 0
Ubuntu:
# This makes the Command key a Control key on Ubuntu
# so you can basically use the same mac shortcuts you
# you are used to
ctrl = super
super = ctrl
halfDuplexCapsLock = false
halfDuplexNumLock = false
halfDuplexScrollLock = false
xtestIsXineramaUnaware = false
switchCorners = none
switchCornerSize = 0
end
section: links
# I set them both to right of each other so I can switch
# with one command
Mac:
right = Ubuntu
Ubuntu:
left = Mac
right = Mac
end
section: options
relativeMouseMoves = true
screenSaverSync = true
win32KeepForeground = false
switchCorners = none
switchCornerSize = 0
# Set this as a mouse button
# So this is (cmd+option+leftclick)
# assuming you are using a Mac keyboard
mousebutton(Super+Alt+1) = switchInDirection(right)
end
Any update on this? I'll be using the config script for now, but would love a native fix
FYI I have manifested this issue on OSX 10.11.1 using Synergy Pro 1.7.5.
The issue is really irritating, how can we increase the priority?
10.11.1/1.7.5
@nbolton @the-wes
Please guys, just bought a license, and this is making the software useless! Please fix the issue.
Thanks
Apple is listed as customer on your site, but this quiet important feature doesn't even work on osx - since 2013 - let's hope that changes soon...
(Other than that - great work)
@nbolton @the-wes
EDIT: Just tried the workaround above - didn`t work for me - is there any know workaround?
Please fix the issue...
Synergy Pro maybe three years more waiting...
PayPal, 18th Oct 2013, $10.00, Successful
@manijak @ekondrashev @sperberAfop some new?
@jujes you should ask @nbolton or @the-wes
My solution right now are 2 keyboards and 2 mice - aka NOT using synergy at all, although I bought the pro version...
Would be good to look at a fix for this.
It is really some annoying bug...I found out after purchase...
Count me in on this one.
Can't believe still seeing no progress on this bug after such a long time.
To me, using hotkey to switch screen is a much better way than moving mouse to edge.
I can confirm upq's workaround works, mac only see hotkeys with primary mouse click. But this causes problems as many times the click is still seen by mac system while switched to client, so when moving mouse in client screen, the mac server side acts as being selecting something.
Issue still persists with synergy-master-stable-d196ec5-MacOSX1011-x86_64.dmg on OS X 10.11.1, works fine when focus is in other client (windows, ubuntu) but fails when on mac server. With DEBUG2 enabled, the keypress is being captured but the hotkey action is not activating.
Like the others above, would appreciate if this is resolved, purchase order #204299
Thanks
@nbolton @the-wes Earlier on in this discussion, some code snippets were posted with a patch that worked for a particular user. I am going to fork the current release and use this as a starting point. Any known gotcha's? I can see that the snippet was posted back in 2014-06-30 so am assuming that it either had side effects or has slipped through the net :)
Pull request added to resolve this at: https://github.com/symless/synergy/pull/5522
For those who want to use a version with the fix applied whilst waiting for it to be resolved in master, see bin.tar.gz at: https://www.dropbox.com/s/f0tohmgefq2xh3o/bin.tar.gz?dl=0
It is the output bin directory tar compressed, inside is Synergy.app alongside the individual executables. Compiled on Mac OS X, El Capitan, Synergy version is 1.8.1-stable-d196ec5
@spurin's fix works perfectly on my machine
The impact of this change has to be determined before we commit. We'll look in to it.
Can we please put a marker on this for a future release, i.e. v.1.8.4-stable or v.1.8.5 milestone?
Using Synergy 1.8.4 (Build Oct 11th, 2016).
Hotkeys are still not working on Mac server.
Same here. Paid support.
@nbolton contacted me via email as I had a support case open for this issue, for reference it said the following "Hi James, I'm really sorry for the delay. I have prioritized your ticket, it's now high priority. You'll hear from us soon. Thanks, Nick". So, fingers crossed, the fix may make it into 1.8.5
Merged upstream in pull request, resolving the conflict with the filename change for OSXScreen.mm
Anyone still having this issue, can you please try this build from @spurin?
http://symless.com/nightly?filter=f4d9faa
@louwers @miraculixx @upq @victorquinn @Jamiermusic @LoganBarnett @ekondrashev @manijak @sperberAfop @jujes @jptaranto @phonemyatt @robbietjuh @fhill122 @xwvvvvwx @newgoliath
Please see http://symless.com/nightly?filter=f4d9faa for nightly build with included fix, please confirm resolution. I will test tonight when home.
Working for me.
Host: Linux Mint 18
Client: Linux Mint 17
Works perfectly fine. Thanks, @spurin!
Host: Mac OS X 10.11.6
Client: Windows 8.1
Not working for me.
Host: OS X 10.11.6
Client: Windows 10 (10.0.14393)
EDIT: Just randomly started working... that's cool. Thanks for the fix!
Not working for me.
Host and Client: Mac OS X 10.10.5.
Adding a keyboard shortcut makes it impossible to switch from one computers
to the other.
On 20 Nov 2016 at 03:53:15, Devin Ryan ([email protected]) wrote:
Not working for me.
Host: OS X 10.11.6
Client: Windows 10 (10.0.14393)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/symless/synergy/issues/3705#issuecomment-261754921,
or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAUW0YVVSMiEXt662EkS29DEi8D589aNks5q_7YbgaJpZM4Ct5Ob
.
Works for me:
Host: MacOS Sierra Version 10.12.1
Client: Windows 7 Enterprise, Service Pack 1
@politicus, apologies, missed you off the roll call earlier when doing the list of people who've had the issue, some questions ... will try and recreate your environment if this issue still persists.
Did you stop/start the server after applying the hotkeys?
What are you using as the hotkeys for switching (I use the FN F combinations keys, not sure if that makes a difference, please try if using different).
Can you confirm the versions for server/client (did you use the nightly build for all?)
Lastly, could you please paste the log output when you press the hotkeys
Works half-way here.
Host: macOS Sierra Version 10.12.2 - Synergy build 1.8.6-rc1-f4d9faa
Client: Windows 10 Pro (1607) - Synergy build 1.8.6-rc1-f4d9faa
Restarted both Synergy clients, restarted both machines.
@manijak @politicus - Commonality in that you are both using Windows 10. Most of the success cases have been without Windows 10.
@forairan - You're the exception, you had success with Windows 10, did you try the hot keys in both directions?
I am not using Windows 10 as I only use Macs.
Le mer. 23 nov. 2016 à 17:39, James Spurin [email protected] a
écrit :
@manijak https://github.com/manijak @politicus
https://github.com/politicus - Commonality in that you are both using
Windows 10. Most of the success cases have been without Windows 10.@forairan https://github.com/forairan - You're the exception, you had
success with Windows 10, did you try the hot keys in both directions?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/symless/synergy/issues/3705#issuecomment-262566709,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAUW0XG4klxf8njCmEpMjc5ndp8j84P7ks5rBGwngaJpZM4Ct5Ob
.
I just installed the nightly build (1.8.6-rc1-f4d9faa) provided in the links above across the 4 systems I use:
Server - Mac OS X 10.11 - Function F12
Client - Mac OS X 10.11 - Function F1
Client - Windows 8 - Function F2
Client - Ubuntu 16.04 - Function F3
I can switch between any of the combinations above without issue.
@politicus - Your reply above had some of the context from Devin Ryan where it mentions Windows 10, hence the confusion. I'm on El Capitan so slightly newer version but no issues for me. What hotkeys did you use (maybe try the Function F keys). Could you please paste the log window from both the server and client when you press the hotkey combination if the problem still persists.
@manijak - I have a Thunderbolt boot disk in which I can boot Windows 10 from my Macbook (what I use as the client), I'll see if I can get that working next
@spurin Sorry for the delay in my reply. I didn't have access to my second Mac.
Working like a charm! Thank you!
I just purchased/installed Synergy today for the first time and realized that I am encountering these same problems - I can't get a single hotkey command to work when focus is on my OS X server (it works coming back from my windows machine). We're way past that nightly build that was working for a few people so I'm surprised to be having these issues. Here are my specs:
Server: MacBook Pro running OS X Sierra 10.12.2, Synergy 1.8.6-stable-2ab21aa
Client: Dell Latitude running Windows 10, Synergy 1.8.6-stable-2ab21aa
Any help would be much appreciated - I only use one display with an HDMI switch so hotkeys are very important to me.
Hi @brusinow
I also use this with a HDMI switch so have the same issues and concerns, hence the pull request that I created with the fix for this problem. The version you're using is broken, can you uninstall it from both the Mac and Windows and reinstall 1.8.6-rc1-f4d9faa on both of them, available from the following:
http://symless.com/nightly?filter=f4d9faa
Please report back status.
This needs to be merged into master going forwards for it to be available by default. We're almost there on this 👍
@spurin,
It does not look like that nightly build is still available at that link - any other suggestions of how I can get it?
-Brent
@celant - can you please advise and reopen the nightly build for this or merge to master? There's positive feedback in many areas on this already, this discussion, the related discussion and in the pull request. I think it's time for this to go live now don't you?
@brusinow - fearing these might go away, I downloaded them all ... Will upload and share
et voila - please see http://www.twitchy.net/Synergy/ for copies of the nightly builds
Thanks @spurin,
I installed the above mentioned nightly build on my machines and am still not able to use any key commands (from my Mac server) other than main keys like Alt, Control, and Shift. I'm currently using these three together to switch back and forth between my two machines but I'm looking to ideally use function keys.
If I'm running OSX Sierra (10.12.2), is the unspecified osx version acceptable? That's the one I'm running.
@brusinow, are you using FN and F keys or just pressing the F keys, I use the function F keys (see my earlier comments) without any issues.
@brusinow, just to also note, I was implicitly using the nightly build relating to my release not the unspecified one, to note, up until yesterday I was running on OSX 10.11, I'd assume therefore you're using the correct one. Others in the thread are using Sierra so I think it's fine. Think you may just have to play with the choice of hotkeys to find a happy compromise. As above, I'm implicitly using the FN + F keys, not just F keys alone.
@spurin Thanks for the followup, I tried reinstalling the specific 10.11 build and still couldn't get it to take numeric FN + F key commands. Fortunately I only have two computers, so I ended up just using CTRL + OPTION + SHIFT as my switch command with switchDoubleTap set to 10ms. Seems to be working well so far.
@brusinow, thanks for following up. At least it's working now which is something and it's great to have a confirmation of Windows 10 success.
@celant - can we get this in master? That covers successful use cases for all platforms now.
I think the issue with your choice of hotkeys is something else. Are you using a Mac keyboard here? Does it actually register the key as FN and the F key on the input? May seem like a lame question but have you also fully stopped and started server after applying (worth possibly trying a kill of synergy and restart also). As I say, I use a pretty similar configuration to yours and my use case is the same. FN F keys work perfectly. Might be worth sharing your config file with the entries if you still want to pursue it further. Also, the log files from the server/client when you press those keys.
@brusinow ... Thinking about it, it may be the switchDoubleTap, I'm using the standard key press option with F keys assigned to each machine
Issue with macOS as server and Win10 as client still present. Cannot switch back to mac from Win10.
Hi @manijak, can you please share your configuration file or at least the hotkey section from the macOS server. Some people on this discussion and the related have expressed success with Windows 10. Some questions. What are you using as the hotkey selector? Is this still whilst using a mac keyboard? could you try one of the Function keys from F1 to F12, trying with FN+F key on the keyboard, can you also try the combination that @brusinow reported success with on Windows 10 (CTRL + OPTION + SHIFT). Let's see from there, otherwise it might be worth going down the verbose logging path to capture what exactly is happening on the server/client, when you press those hotkeys.
Just updateing: No reaction for keyboard definitions on the server (tried F14 and F15)
Server OS X El Capitan
Client maxOS Sierra
Synergy 1.8.7-stable-9799e96 (19.January 2017)
@KjellMorgenstern : it's not in 1.8.7 or any upstream release as yet. Can you please try 1.8.6-rc1-f4d9faa which has the hotkey fix I put the pull request in for. If the links earlier in the thread do not work, I have a mirror of them here - http://twitchy.net/Synergy/
Please let me know how you get on.
@spurin : I can confirm the patched version works. I replaced 1.8.7 with synergy-pr-5522-hotkey-rc1-f4d9faa-MacOSX1011-x86_64.dmg on my server. The client is still running 1.8.7. I did not modify the configuration, just started 1.8.6-rc-f4d9faa from 18.Nov.2016, and it worked.
My configuration is currently "shift-f15" switch to client "f15" switch to server. I did not find a readable configuration file, my configuration was created with the frontend, and is probably stored in a plist file (or did I miss something about the config file?)
@spurin I can also now confirm that the patched version works in combination with macOS Sierra and Windows 10. I am using the following hotkeys:
"Shift-F13" = switch to Win10 (client)
"Shift-F15" = switch to macOS (server)
Have no idea why it didn't work earlier. Could be that I had a beta version of Sierra OS.
Thanks a lot for your effort mate!
@Celant @nbolton @nlyan @XinyuHou : Can we please push forward to get this into a public release now, we've got a general consensus with the feedback above and also the positive feedback on https://github.com/symless/synergy/pull/5522
There's no reason not to get this in and it's been outstanding now for years!
People like myself are having to rely on the 1.8.6 nightly build and one that I'm having to host for myself at the moment to get round what is a very frustrating issue.
Further to this, because of the release to 1.8.7, it breaks the 'Pro' functionality when having to use 1.8.6, functionality which I personally have paid for to get SSL support. When it checks for updates it seems to disable the Pro functionality and you need to re-activate it...
I for one, want to be able to download the latest version and use it as expected.
@spurin You are so right about that:
I for one, want to be able to download the latest version and use it as expected.
I lost quite some time understanding the Pro functionality was broken because I was using 1.8.7. version.
Very frustrating.
In this https://github.com/symless/synergy/pull/5796 it was originally earmarked for 1.8.7 (that never happened, and then it was changed to 1.9.x beta ... not 1.8.8?).
If we're lucky, we might get it by 1.9.9 at this rate but that's looking like a big if based on current feedback and failed promises.
Can we please get this added to 1.8.8? Very disappointing if I have to go down the route once again of compiling a release manually with this fix in order to get functionality that have paid for.
Welp. I just blew a good half hour trying to get hotkeys to work between two macs, before coming on and finding this. Golly, will it make it to three years without a fix?
@WibbletheDuck, welcome to the club, enjoy using 1.8.6 to get the hotkey functionality that you desire that's been broken for 2 years+
I've pretty much resigned to this not being resolved having gone through a multitude of efforts in this thread, and the others, to support this, not to mention, verifying that this works across all platforms. I've also offered Symless direct testing and feedback to which they've not followed up further.
Even though I paid for the product, I can't use the pro functionality as the SSL implementation in the version with the fix is flakey, not to mention the new version check seems to lose the pro functionality each time.
If it goes to 3 years without a fix, or again, a major release is made without this fix, I'll be forking my own version, with said fix and will track upstream.
This time though, the download link won't be in the thread as it is above. It will be provided to each person, after a followup/complaint has been made in some shape or form to Symless that this issue is still affecting people.
I'm out of ideas on what to do here, there is radio silence in most cases from Symless and correspondingly, they seem to continuously triage issues that seem to affect individuals (like an odd Japanese key not working), rather than widespread issues that have been outstanding for two years (with extensive complaints, comments, fixed code via their users, feedback stating success .. yada yada) ...
I can confirm that the version @spurin provided above for 1.8.6 does, indeed work. I'm connecting from OSX 10.12 for the server to a client running Windows 10 and it works fine. (except that the key-mapping UI seems to confused about which key is which, but that's fine)
@spurin thank you so much for all of your work on this and I really hope that Symless folks finally pay attention to this thread. (though, after 3 years, I'm not holding my breath)
So I just purchased Synergy Pro and this feature doesn't work? And a fix has been sitting around in #5796 with no update for 6 months?
@nbolton ples
@spurin i appreciate you effort and time, all the links above are broken to download this fix and like you this is a frustrating issue. Any assistance would be appreciated.
I'm loathed to help out on this anymore given that Symless have made a bunch of promises that they don't keep... not to mention, being a pro customer stuck on an old release. Very annoying that I'm more interested in helping people with this than they are.
@WibbletheDuck @EasyAsABC123 I'll help you out with links to a Mac version that has the fix, can you email me ... its my first name which is james at my github userid dot com
Still broken for me. Definitely don't want to give up SSL for this feature, though.
3 years since issue opened, and over 6 months with a fix (submitted by a user) sitting in PR 😒
The fix provided by @spurin solved my issue, this should be merged into master...the fact that it hasn't been properly reviewed and merged can only be described as lazy and negligent.
@nbolton
The update by @EasyAsABC123 again, proves this fix is valid, it is the latest version of Mac OS X as the server. There's been plenty of time now to review this PR... now that game of thrones has finished this season, maybe give a bit of love back to your supporters and fix this once and for all? Winter is coming...
Please make this a Must or at least a Should, rather than a Could - https://github.com/symless/synergy/projects/4
@spurin the way to get onto that list, which i believe is completely a bad idea...is based of thumbs up on the first post in the issue...
If you want this fixed...please add a reaction to the top post...
Because they are fixing bugs via this GitHub Sort which completely ignores this bug...
Go to the top and add a reaction (top right of the post...)
@spurin Any way I can get a link to the download that actually works? I'm testing with MacOS High Sierra and Windows 10. Thank you for your efforts!
@smidley - Here you go, please let me know if you have problems and report back if it's working for you. You should be okay, I'm on High Sierra, latest version, and also using Windows 10 with latest updates. You need to bounce the server after applying hotkeys.
It was not working at first but after changing the hot keys a number of times it seems to be working now. However, while in a game on the windows client, I have no mouse movement and the keyboard presses are very delayed.
On Dec 21, 2017, at 3:05 AM, James Spurin notifications@github.com wrote:
@smidley - Here you go, please let me know if you have problems and report back if it's working for you. You should be okay, I'm on High Sierra, latest version, and also using Windows 10 with latest updates. You need to bounce the server after applying hotkeys.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
@smidley - the hotkeys are trial and effort and some key combinations work better than others, I've had success using the F keys on a mac keyboard. I think the issue with the mouse movement and keyboard delays are more a synergy issue than a hotkeys issue. Are you using it over wifi? I found that certain network intensive activities like backups etc or possibly gaming, can affect the use of synergy and given the bi-directional nature of wifi, problems are much more apparent when using this, I'm using a dedicated hard wired network now for Synergy and it works well.
Thanks for the info. I am on WiFi with no easy way to go to a wired connection.
On Dec 31, 2017, at 5:03 AM, James Spurin notifications@github.com wrote:
@smidley - the hotkeys are trial and effort and some key combinations work better than others, I've had success using the F keys on a mac keyboard. I think the issue with the mouse movement and keyboard delays are more a synergy issue than a hotkeys issue. Are you using it over wifi? I found that certain network intensive activities like backups etc or possibly gaming, can affect the use of synergy and given the bi-directional nature of wifi, problems are much more apparent when using this, I'm using a dedicated hard wired network now for Synergy and it works well.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Most helpful comment
Anyone still having this issue, can you please try this build from @spurin?
http://symless.com/nightly?filter=f4d9faa