Synergy-core: Some keys don't work for macOS Sierra clients

[grigorovich]

Server: Synergy server v1.8.2-stable-130a248 ; MacOSX 10.11.6 / macbook air
Client: Synergy client v1.8.2-stable-130a248 ; MacOSX 10.12 GM / imac
Scancode application: Many Tricks - Key Codes v2.1

Some keys:
CTRL + Up (Mission Control)
CTRL + Down (Application windows)
CTRL + Left (Switch to left desktop if you have additional virtual desktop)
CTRL + Right (Switch to right desktop if you have additional virtual desktop)
F11 - Show Desktop (if checked in system preferences)
FN+F3 ; FN+F4 (or just F3/F4 button like standard mac keyboard)

They does'n send by SynergyServer correctly or doesn't receive by SynergyClient correctly...

So i made small investigation with. For example i traced key F1 in 3 steps - server keyboard scan, client synergy scan, client keyboard scan:

1) Scancode application on server - just server's keyboard:

Unicode: 63236 / 0xf704
Keys: F1
Key Code: 122 / 0x7a
Modifiers: 8388864 / 0x800100 <<<<<<<<<<<<<<
Modifiers Description:
NX_SECONDARYFNMASK / kCGEventFlagMaskSecondaryFn / NSFunctionKeyMask
= 8388608 / 0x800000
NX_NONCOALSESCEDMASK / kCGEventFlagMaskNonCoalesced
= 256 / 0x100 <<<<<<<<<<<<<< That attribute is absent in 2) situation below

2) Scancode application on client - receive server's Synergy keyboard scancode:

Unicode: 63236 / 0xf704
Keys: F1
Key Code: 122 / 0x7a <<<<<<<<<<<<<< OK (Same) but...
Modifiers: 8388608 / 0x800000 <<<<<<<<<<<<<< ?? Not same
Modifiers Description:
NX_SECONDARYFNMASK / kCGEventFlagMaskSecondaryFn / NSFunctionKeyMask
= 8388608 / 0x800000
<<<<<<<<<<<<<< ?? Absent/Where?

3) Scancode application on client - just client's keyboard:

Unicode: 63236 / 0xf704
Keys: F1
Key Code: 122 / 0x7a <<<<<<<<<<<<<< OK (same)
Modifiers: 8388864 / 0x800100 <<<<<<<<<<<<<< Present. Same as 1)
Modifiers Description:
NX_SECONDARYFNMASK / kCGEventFlagMaskSecondaryFn / NSFunctionKeyMask
= 8388608 / 0x800000
NX_NONCOALSESCEDMASK / kCGEventFlagMaskNonCoalesced
= 256 / 0x100 <<<<<<<<<<<<<< Present

In 3rd situation result of native mac keyboard on client same as native mac keyboard on server.
But in 2nd situation synergy client did not received additional attribute like 0x100.

[Jayceh]

Just found this same behavior. Running 1.8.2, linux server, mac client. Was working, just upgraded the mac to sierra and now do not get ctrl to work in any hotkey sequence. Ctrl does work when mouse-clicking though. Something specifically when upgrading to Sierra.

[neybar]

I'm having this same problem. With linux 1.8.2 server and mac Sierra client, the Ctrl key doesn't seem to register.

[dugger]

Same problem, but I've noticed that Ctrl + (0-9) still works.

[Kenblair1226]

Same here, Ctrl + UP, DOWN, LEFT, RIGHT do not seem working.

[tybritten]

Same here, Sierra Client, El Capitan Server. 1.8.3-rc2-89c9c58

[alanhoyle]

I am having trouble with cmd+left/right/up/down. Note that the Keyboard viewer does, in fact, display that I'm pressing cmd-left (e.g.), but the UI doesn't respond.

[Jayceh]

As an added note, on a different set of machines, 1.8.2 across the board, Sierra server to Linux client, the keys work fine, but with Sierra server and Sierra client, it also doesn't work. So very specifically a Sierra _client_ issue.

[nlyan]

Thanks guys. This is obviously a regression and will be a priority for 1.8.4

[alanhoyle]

Weird thing: the keyboard viewer switches from a 105 key layout (if I hit a key on the 105 key external attached to my mac client) to a 77 key layout if I hit a key on the linux server keyboard.

[stephenotalora]

hi guys any updates on this? has the issue been resolved as part of v1.8.4? and if so when will it be released?

[focalintent]

From doing some digging/testing on my machines here - it appears to be less about key combinations not going through and more about certain mission control actions not getting triggered properly by synergy. If I change the keyboard shortcuts for mission control (or pagination between desktops) to other keyboard combinations - they still get ignored. Ditto the function key options for triggering mission control (among other things) - so I think this is less about the specific key combinations and more about sierra ignoring synergy as a source of events that trigger mission control/virtual desktop events.

[ivelrrat]

@focalintent I'm not sure it's about mission control. I use a window helper called shiftit that changes your window size with keyboard shortcuts. all the shortcuts work except for the ones that use the arrow keys (all shortcuts by default start with cmd+opt+ctrl). This started with updating to sierra. it works when I use my native keyboard but not synergy.

[andrewr01]

@ivelrrat I agree, I haven't been able to use the arrow keys with mission control. Like @grigorovich posted initially.

But the following DO work:
Switch to Desktop 1 = ctrl + 1
Switch to Desktop 2 = ctrl + 2

I have changed the "Move left a space" and "Move right a space" shortcuts to ctrl + L and ctrl + R and they work.

Also changed the non-functional "Show Desktop" = F11 to command + D and Mission Control to ctrl + alt + M

[focalintent]

I'll try again tomorrow on my setup - I was having none
of the key combinatIons that I tried working. (Ditto swipe gestures for switching desktops, for that matter)

[icorbett]

I went ahead and tried reverting to each stable release from 1.8.4 back through 1.7.2 and believe I have exhausted the possibility that this is a regression but instead a new behavior of Siera (10.12).

Both when _successfully_ setting Keyboard Shortcuts in System Preferences to use CTRL + Up, CTRL + Down, CTRL + Left, CTRL + Right; and _unsuccessfully_ trying to trigger those same key sequences, I see the following message in the synergy Log:

[2016-10-11T13:34:37] INFO: found key in group 1

For the record I am using synergys built directly from git tags on a Linux machine and synergyc on macOS Siera (10.12) installed from dmg images.

[cocacrave]

having same issue since macos sierra. i saw the update for 1.8.4 and got excited to see if it was fixed but i guess next version?

[dgmiller81]

All -

I am able to confirm the same behavior. Config below:

• Windows 10 Pro (server) running [Synergy 1.8.4-stable]
• OS X Sierra 10.12 (client) running [Synergy 1.8.4-stable]

Just wanted to share for reference. That is all.

[icorbett]

There appears to be a build of synergy-v1.8.5-stable-984ca48 today (http://symless.com/nightly?filter=1.8.5) but it appears to be a mistake, while 984ca48 does appear to be a valid commit (in github but not in history with a git pull) the version information in the package says 1.8.4-stable-984ca48, it also doesn't appear to fix issue #5592.

[focalintent]

Following up with my own setup here -- if I go into keyboard | shortcuts on my client mac and set the key commands for move left/move right to ctrl-cmd-[ and ctrl-cmd-] then those are working over synergy. Apparently the initial set of alternate key commands I was trying to use were things that were still filtered.

(Note that multi-touch gestures are still completely lost - in my setup both host and client machines are macOS sierra machines)

PS. HI @icorbett :)

[chevtek]

I'm having the same issue after upgrading to Sierra. Googled and couldn't find anything because I kept searching for "OS X Spaces not working with synergy" or variations of that query (mentioning my search here in case others do the same). I hadn't thought to search for "synergy sierra mission control" until today and now here I am. Glad I'm not the only one as it's been driving me crazy.

I'm using Windows 10 as the host and my Macbook Pro with OS X Sierra 10.12 as the client. This began immediately after upgrading to Sierra. I've tried several older versions of Synergy client & host and they all have the same issue up through the current stable build.

It does not matter what keybinding I choose in the mission control preferences. They are all ignored. The odd thing is that the arrow keys clearly work as I can arrow around text and other things on my macbook using the arrow keys on the host machine. I can also use Ctrl just fine for other things like copy, paste, or killing programs/clearing the screen in OS X terminal.

One thing to note is that there is a second dropdown in mission control keybindings that has a couple mouse options for accessing mission control. I tried setting that to "Middle Mouse Button" and that actually worked over Synergy. I turned it back off because I don't particularly like using my middle mouse button for that, but it did indeed work.

[andrewr01]

These keys work for me over Synergy, just the original settings which are the same as your screenshot don't work for me, and any combination that uses arrow keys in the mix.

[chevtek]

Interesting. I tried to use F1 and Left control and they did not work. I didn't go through the entire list though. I guess I should have.

[chevtek]

Actually, how did you choose a letter key as an option? I can't seem to be able to use anything other than the predefined choices.

[andrewr01]

System Preferences > Keyboard > Shortcuts > Mission Control

[alanhoyle]

In any web-based applications the COMMAND-left/right are getting interpreted as "back/forward" respectively and taking me to the previous/next web page when sent through Synergy. Everything works as expected with the native keyboard. I've tested in Chrome, Safari, Firefox, and Mailplane (a gmail browser app).

[rdamazio]

Even more interesting - if I use System Preferences > Keyboard > Shortcuts > Mission Control to assign a shortcut, and press F11 over synergy, it captures that as the shortcut! But then actually using it fails.

[MattzFiber]

Can confirm I am having this too
CMD - Arrows are totally not working for me at all :(

[sness]

Confirmed not working for me as well

[chevtek]

@andrewr01 thanks! Confirmed that works. I was at least able to do that and map those combinations to left and right tilt on my mouse wheel. At least I have a workaround. Was driving me crazy.

[cocacrave]

@chevex how did you assign left/right mouse tilt to move left/right space? could you walk me through?

[chevtek]

@cocacrave oh I just have a Logitech mouse with mappable buttons. The mouse wheel on it tilts left and right and I used to map those buttons to ctrl + left arrow and ctrl + right arrow. Those keys don't work over synergy anymore but thanks to @andrewr01 I was able to go to system preferences > keyboard > shortcuts > mission control and map "ctrl + option + L" and "ctrl + option + R" to move spaces left and right and those seem to work over synergy so I was able to map the new keys to my mouse wheel tilt buttons.

[Rimbo]

Upgraded to 1.8.5. Issue remains. (Created duplicate issue 5708; that one can be closed.)

[XinyuHou]

Hi guys,
Could you test our latest 10.12 build on your sierra to see if the problem persists? Thanks.
http://symless.com/nightly?filter=synergy-v1.8.6-rc1-7ce6905

[mcg]

Still broken for me with synergy-v1.8.6-rc1-7ce6905.

[markrcote]

Still broken here as well. Both server and client running synergy-v1.8.6-rc1-7ce6905.

[tybritten]

Same. When I let CTRL & Arrow all I get is “found key in group 0” in the log.

On November 1, 2016 at 11:43:46 AM, Mark Côté ([email protected]) wrote:

Still broken here as well. Both server and client running synergy-v1.8.6-rc1-7ce6905.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[Rimbo]

Same as the above. "found key in group 0," no luck. Had 1.8.6-rc1-7ce6905 on both client (10.12) and server (10.11).

[icorbett]

I also see the same behavior as before with synergy-v1.8.6-rc1-7ce6905 on both macOS Sierra (10.12.1) client and Linux server however I continue to get the following error which is slightly different from what it appears others are seeing:

[2016-11-02T10:19:16] INFO: found key in group 1

[Gatsby-Lee]

I have same issue. I'm using v1.8.5.
For now, I add Mission Control in Dock so that at least I can access that functionality.

[solokacher]

1.8.3 and 1.8.5 client on macOS Sierra has the same problem on my side. Slash "/" also doesn't work.

[paintedballerina]

1.8.5 installed on both machines. Sierra server | Win7 client.
Mouse works, clicking mouse works... no keystrokes.

[ihji]

+1

[Unzensiert]

+1

[moexius]

Any updates? I have tried to remap the keys arrow left/right + ctrl to something else, not even using ctrl at all, but I believe the issue is with synergy not properly tapped to application switching.

[sandinak]

Sys Eng/Coder here.. I can has the same problem.. tried to switch my ctrl char ... I've been using ctrl-arrow since fvwm2 days .. can't break the habit. Any assistance I can give.. I am more than willing to help out..

[sandinak]

All... FWIW .. I filed a bug on this a whilst back.. i know they're on it ;)

[XinyuHou]

Hi guys, thank you for all the feedbacks. We are still investigating this issue. So far, it seems macOS Sierra does not support some keys simulation with its native Core Graphic function CGEventPost . Those keys are Mission Control, Launchpad and Option-Command-Escape. We are trying to find if there is any alternative way to simulate that. Thanks for your patience.

[XinyuHou]

Hi guys, can you test this nightly for Mac? It's valid for Mac 10.9 and above.
http://symless.com/nightly?filter=synergy-issue5592-ctrl-up-key-rc1-e8145aa-MacOSX-x86_64.dmg

[andynu]

@XinyuHou: 💚 I was experiencing the F1 key not working in macOS Sierra 10.12.1. This nightly release fixed the issue in my context. Wonderful!

[Gatsby-Lee]

@XinyuHou I tested Mission Control functionality with key ( ctrl + up ) and switching desktop with key ( ctrl + left and right ). It works well. thank you. plz let us know if it goes into stable version. great job.

[mcg]

Ctrl+left/right is working again for me! Thanks for the fix.

[moexius]

Same here. So far so good. Mission control works again! thanks for the fix.

[dugger]

👍 Thank you!!

[AndreasDolphin]

Had the same issue with 1.8.2, the linked nightly build fixed it for me :D

[XinyuHou]

Thank you for the feedbacks, guys.

@gservice
Yeah, it will be in our next stable release which would be in 3 weeks. Please sit tight. Thanks for your patience.

[AndreasDolphin]

As a side note as I just seriously started using my work Macbook, while CMD+Up/Left/Right works through Synergy, I use those a lot, taking screenshots seems wonky. CMD+Shift+4 that's used for snapping regions only reacts on the laptop keyboard and not from my Windows host. Related?

[XinyuHou]

@AndreasDolphin
Which version of Synergy are you using?

[AndreasDolphin]

Just checked, 1.8.3-stable-db9181b on the server side, Windows, basic. I was going to update but didn't want to close down all the required applications just yet :P Maybe on Friday. The Mac client has version 1.8.6-rc1-e8145aa which fixed the other keys.

[XinyuHou]

@AndreasDolphin
Please update your server to the latest stable. I have tried on my Windows 10 server and Mac 10,12 client. CMD+Shift+4 works to get regional screenshot.

[AndreasDolphin]

Server is now running 1.8.5-stable-a18eba7, issue persists. Not sure if there is any log I can look at to see what's going on except for what is printed in the client window.

[XinyuHou]

@AndreasDolphin
Please create a new issue and use our template to put as many details as possible. Some logging from both server and client would be helpful. Thanks.

[Adam2Marsh]

Hi @XinyuHou

Tested the MacOs Nightly build and the issue is not resolved for me.

I'm running Ubuntu Host 1.8.5 Stable, when pressing control left or right on the mac I still just see the found key in group 0.

[XinyuHou]

@Adam2Marsh
Please let us know your OS and Synergy verison info. Logging from both your server and client would be helpful. Please use Debug2 log level. You can change it in Edit->settings->Logging on Ubuntu and Synergy->Preferences->Logging on Mac

[stephenotalora]

Thank you @XinyuHou works perfect Mac to Mac! happy camper here 👍

[andrewr01]

Fixed for me with the nightly BUT ... Now when I use Parallels Client to RDP to my Windows Server, no Windows key is sent. Parallels Client is set to use CMD for Windows Key. I have reverted to 1.8.5 stable on Mac Sierra client as I need the Windows key and can configure non-default keys for switching desktops on the Mac.

[tybritten]

Yup. using the synergy-issue5592-ctrl-up-key-rc1-e8145aa-MacOSX-x86_64 build on 10.12 client with 10.12 server and keys are working again

On November 27, 2016 at 1:56:11 PM, Jonathan ([email protected]) wrote:

Thank you @XinyuHou works perfect Mac to Mac! happy camper here 👍

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[andrewr01]

Fixed for me with the nightly BUT ... Now when I use Parallels Client to RDP to my Windows Server, no Windows key is sent. Parallels Client is set to use CMD for Windows Key. I have reverted to 1.8.5 stable on Mac Sierra client as I need the Windows key and can configure non-default keys for switching desktops on the Mac.

[focalintent]

Another vote for this working between macOS sierra machines - now, if only the trackpad gestures would go across...

[Rimbo]

The nightly works for me as well.

[doowb]

Today Cmd+Tab stopped working on my client machine.
The nightly (from Nov 22, 2016) fixed this, along with any issues I had with arrow keys.

[XinyuHou]

Merged in to 1.8.6

[alanhoyle]

Just wanted to report that this is indeed fixed in 1.8.6 for me. Thanks again!

[lparsons]

Working for me as well, thanks!

[alanhoyle]

I just wanted to report that this version also appears to have fixed the
"cmd-option-escape doesn't bring up Force Quit" issue that I've had for
years. Thanks!

--

• Alan Hoyle - [email protected] - http://www.alanhoyle.com/ -

On Mon, Dec 12, 2016 at 4:42 PM, Lance Parsons [e-mail]
wrote:

Working for me as well, thanks!

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/symless/synergy/issues/5592#issuecomment-266561933,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AARr8x3ADfUyj0tMegpnXdOvTw5ezvqTks5rHb_jgaJpZM4J5_8t
.

[EmmanVazz]

This update works for me as well. Thanks!

[XinyuHou]

@DarcieF
Sorry for the inconvenience.

Could you create a new issue with reproduce steps? Then we can look into the cause. Thanks.

[intel352]

Similar issue exists for me in 1.8.6, I'm unable to take a screenshot on an OSX client from an OSX host, i.e. - CMD+SHIFT+4 to trigger a select-area screenshot. The host intercepts the command every time despite cursor focus on the client.

[wwboynton]

I'm still experiencing this problem in 1.8.8, using a Sierra host and an El Cap client. Using the Keyboard Viewer, presses to the control key simply don't register.

It seems to be the same issue of host intercept, because I usually have some key remapping on (I eventually took it off to see if that was causing the issue and it was not) and I could see the control key getting pressed when I hit my physical command key.

[grigorovich]

All keys works. Even do FN+F11/F12 for example. But have some issues with some applications:
Parallels (windows 10) - CMD (win key) doesn't
UnrealEngine, Blender - some combinations like SHIFT+LMB or CMD+LMB doesn't.

But in Finder Shift+LMB works.

Server 1.8.8, MacOS
Client 1.8.8, MacOS

[morinted]

@XinyuHou I'm working on an unrelated project and I think I made a discovery that might help. This is not using the lower level HID calls…

I was able to get command/control keyboard shortcuts working again by adding kCGEventFlagMaskSecondaryFn to the modifier event flags when the target key code was >=53 (escape) but not a modifier (55-63). Not looking for a fix myself, just saw that you guys had a similar issue. All the best!