Jump to content

MacOs Sierra Client Control key not functioning


Bill Chen

Recommended Posts

Hi All,

 

This was mentioned on this thread, viewtopic.php?f=16&t=1955#p5626, but I think it's getting lost in all the clutter so figured I'd create a new thread and see if anyone has any thoughts.

 

I have a Win7 Server, with a MacOs Sierra Client running 1.8.3 Stable.

 

When I'm on the client, the control key modifier doesn't work as expected:

[*] Ctrl + Up (Mission control) - No action

[*] Ctrl + Down - No action

[*] Ctrl + Left/Right (switch VM views) - in a text editor moves to the front/end of a line like the command key modifier would

 

Looks like the Control key has lost it's binding with a MacOs Sierra client. Any thoughts on how to fix this?

 

Thanks in advance,

Bill

Link to comment
Share on other sites

Just a quick update. :)

 

control + 1,2, or 3 (Switch to Desktop Keyboard Shortcut) is my current work around not being able to use control + left/right arrows.

 

So it seems with Sierra and Synergy, the control modifier with the arrow keys (up/down/left/right) is broken.

 

Can anyone else confirm?

Link to comment
Share on other sites

Lyndsay Weitzel

Same issue here, on a similar setup:

 

Windows 10 server, 1.8.3 stable

MacOS Sierra client, 1.8.3 stable

 

Setting shortcuts in the mac's keyboard preferences from the server's keyboard always works, but some key combinations don't work when you want to use the shortcut. (switching mission control desktops, for example)

 

control + left or right arrow does not switch desktops

control + [ or ] does switch desktops

 

command + left or right arrow does not switch desktops

command + [ or ] does switch desktops

 

The arrow keys by themselves work, such as when moving the cursor to write this post.

Issue appeared after updating to Sierra.

Link to comment
Share on other sites

Thanks for the helpful thoughts Lyndsay.

 

I've now just remapped my desktop switch commands to control + [ and ] and mission control to control + m.

 

As a side note, it seems I can't get F12 to work to open the Dashboard...although not really using that anyways. :)

 

Bill

Link to comment
Share on other sites

  • 2 weeks later...
HOU Haixiang

Thanks very much. Great help for me :D

 

Same issue here, on a similar setup:

 

Windows 10 server, 1.8.3 stable

MacOS Sierra client, 1.8.3 stable

 

Setting shortcuts in the mac's keyboard preferences from the server's keyboard always works, but some key combinations don't work when you want to use the shortcut. (switching mission control desktops, for example)

 

control + left or right arrow does not switch desktops

control + [ or ] does switch desktops

 

command + left or right arrow does not switch desktops

command + [ or ] does switch desktops

 

The arrow keys by themselves work, such as when moving the cursor to write this post.

Issue appeared after updating to Sierra.

Link to comment
Share on other sites

  • 2 weeks later...
A. Elaine Van Der Wall

Just wanted to note that I'm experiencing the same issue. Mac OSX Sierra client with Windows 10 x64 server, Control + Arrow keys doesn't switch desktops like it did previously. And F12 doesn't show all the windows anymore either (I forget what that's called lol). I just downloaded and installed synergy-master-stable-a6ff907 from the Nightly builds and it didn't fix the problem.

 

Thanks for the tip on changing the OSX shortcut to use a different key, that's a major part of my workflow too and moving to my client's keyboard (it's a laptop) every time I need to move desktops was slowin' me down! :D

Link to comment
Share on other sites

Johan Jeffery

Just another report of the same issue. The start of the problem is with the Sierra update. This happens also with Synergy 1.8.2 and 1.8.4. I have a similar configuration, i.e. Windows 7 64-bit as a server with a Mac OSX Sierra client.

Link to comment
Share on other sites

Romar Mayer Micabalo

I have a similar issue wherein ctrl + arrow key do not work on the client. I am using an OS X El Capitan (10.11.6) as the Synergy server, and an macOS Sierra (10.12) as the Synergy client.

 

I have Synergy 1.8.4 .

Link to comment
Share on other sites

Michael Clark

I have the same problem. I've got Ubuntu 16.04 as the Synergy Server and Mac OS 10.12 as the Synergy Client. Synergy is 1.8.4-stable-a6ff907. I can see the key being sent across in Debug1 but it doesn't appear to be used.

 

2016-10-20T11:15:13] DEBUG1: recv key down id=0x0000efe3, mask=0x2000, button=0x0025
[2016-10-20T11:15:13] DEBUG1: mapKey efe3 (61411) with mask 2000, start state: 0000
[2016-10-20T11:15:13] DEBUG1: find best:  0000 2000
[2016-10-20T11:15:13] DEBUG1: best key index 1 of 1 (exact)
[2016-10-20T11:15:13] DEBUG1: found key in group 0
[2016-10-20T11:15:13] DEBUG1: state: 0000,0000,0000
[2016-10-20T11:15:13] DEBUG1: flip: 0000 (0000 vs 0000 in 0000 - 0000)
[2016-10-20T11:15:13] DEBUG1: desired state: 2000 0000,0000,0000
[2016-10-20T11:15:13] DEBUG1: flip: 0000 (0000 vs 2000 in fffd - 6020)
[2016-10-20T11:15:13] DEBUG1: mapped to 03c, new state 0002
[2016-10-20T11:15:13] DEBUG1: keystrokes:
[2016-10-20T11:15:13] DEBUG1:   button=0x003c virtualKey=0x003b keyDown=down client=0x0000
[2016-10-20T11:15:14] DEBUG1: recv key down id=0x0000ef51, mask=0x2002, button=0x0071
[2016-10-20T11:15:14] DEBUG1: mapKey ef51 (61265) with mask 2002, start state: 0002
[2016-10-20T11:15:14] INFO: found key in group 0
[2016-10-20T11:15:14] DEBUG1: state: 0002,0000,0000
[2016-10-20T11:15:14] DEBUG1: flip: 0000 (0002 vs 0000 in 0000 - 0000)
[2016-10-20T11:15:14] DEBUG1: desired state: 2002 0002,0000,0000
[2016-10-20T11:15:14] DEBUG1: flip: 0000 (0002 vs 2002 in ffff - 6020)
[2016-10-20T11:15:14] DEBUG1: mapped to 07c, new state 0002
[2016-10-20T11:15:14] DEBUG1: keystrokes:
[2016-10-20T11:15:14] DEBUG1:   button=0x007c virtualKey=0x007b keyDown=down client=0x0000
[2016-10-20T11:15:14] DEBUG1: recv key up id=0x0000ef51, mask=0x2002, button=0x0071
[2016-10-20T11:15:14] DEBUG1: keystrokes:
[2016-10-20T11:15:14] DEBUG1:   button=0x007c virtualKey=0x007b keyDown=up client=0x0000
[2016-10-20T11:15:14] DEBUG1: recv key up id=0x0000efe3, mask=0x2002, button=0x0025
[2016-10-20T11:15:14] DEBUG1: new state 0000
[2016-10-20T11:15:14] DEBUG1: keystrokes:
[2016-10-20T11:15:14] DEBUG1:   button=0x003c virtualKey=0x003b keyDown=up client=0x0000

 

Hadn't thought of using Ctrl-1, etc. Will give that a try.

 

After trying that. It still didn't work. If I switch the Mac to be the Server and Ubuntu to be the Client, then ctrl-alt-arrow will change the screen on Ubuntu. FYI, ctrl-alt-arrow are the default for Linux while ctrl-arrow are the default for Mac so I just leave the host's keyboard mappings alone and require myself to remember what type of OS my cursor is currently on.

Link to comment
Share on other sites

  • 3 weeks later...
Brian Sayatovic

I, too, think I am having this problem. I thought I was crazy and alone, but this thread is vindicating me.

 

I'm running 1.8.5 on my server (Windows) and client (Mac OS X Sierra). I had Ctrl+Alt+Cmd+Arrow set in Mac OS X Optimal Layout to move my windows to the left/right halves of the screen. It works from the native Macbook keyboard. And when I'm in a preferences screen configuring a keystroke, it detects it.

 

But when I try to use the keystroke to do the assigned function, nothing happens.

 

When I changed to a non-arrow-key (e.g. "[", "]"), it works fine.

Link to comment
Share on other sites

Same issue here ever since updating to Sierra.

 

Using Synergy 1.8.5-stable-a18eba7

Server: Window 8.1

Client: OSX Sierra

 

When using the keys I see this on the Synergy log on the client:

 

[2016-11-10T10:39:16] INFO: found key in group 0
[2016-11-10T10:39:17] INFO: found key in group 0
[2016-11-10T10:39:17] INFO: found key in group 0
[2016-11-10T10:39:17] INFO: found key in group 0
[2016-11-10T10:39:17] INFO: found key in group 0
[2016-11-10T10:39:18] INFO: found key in group 0

 

Currently using Command+Tab as a work around.

Link to comment
Share on other sites

  • 4 weeks later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...