Hash (#) key not working (UK keyboard, win7 server, mac client)

[nbolton]

Imported issue:

• Author: Peter Choo
• Date: 2012-05-02 13:09:41
• Legacy ID: 3197

Steps to reproduce:

1. Open TextEdit
2. Press # key

Expected: # symbol appears in text edit
Actual: Something completely different:

1.4.6: Command+3 combination sent instead
1.4.7: Command+3 combination sent instead
1.4.8: Numeric 3 sent instead

Interestingly, on 1.4.8 if I press alt+# (option+# on the mac) I get the hash symbol. Shift+# gives me the ~ symbol (expected behaviour).

Versions (Synergy, OS):

Server: 1.4.8 Windows 7 64-bit
Client 1: 1.4.6-8 Mac OS X Lion 10.7.3

Workaround:

Downgrading to 1.3.8 client on the mac (with 1.4.8 server) has worked for me.

Option+# gives me the # symbol in 1.4.8 and 1.4.7. I didn't test this in 1.4.6.

I am currently using 1.4.7 so that I can use the right shift, and click + drag.

Comments:

Although this has now once again disabled my ctrl+drag ability on the mac, which was the reason for the upgrade in the first place.

[nbolton]

• Author: Thorben Glck
• Date: 2012-06-26 12:23:02

Same problem occurs on 1.4.8 Server on Mac OS X Lion 10.7.4 and 1.4.8 Client on Mac OS X Lion 10.7.4. Is there a workaround until this has been fixed, which does not include installing an older version?

[nbolton]

• Author: David Philip Gsenbauer
• Date: 2013-06-24 06:02:50

This still is an issue with 1.4.12 Server on Mac OS X Mountain Lion 10.8.4 and 1.4.12 Client on Mac OS X Mountain Lion 10.8.2.

[nbolton]

• Author: Daniel Scheikl
• Date: 2013-08-05 09:37:15

I can confirm this bug for Synergy 1.4.12 on Mountain Lion. Also on my german keyboard SHIFT+# should give you the apostrophe ( ' ) but instead prints another apostrophe ( ` ), what is very annoying when writing english texts.

[nbolton]

• Author: Tobias Haeberle
• Date: 2014-04-14 13:34:24

The bug is also present in 1.4.17: Server OS X 10.7.5, Client: OS X 10.8.5, language German, keyboard layout German

Pressing the hash key "#" on the server gives you a "3" on the client....

[nbolton]

• Author: Chris Ferebee
• Date: 2014-04-27 18:20:21

I have the same problem with 1.4.17 server on OS X 10.8.5 and 1.4.18 beta client on OS X 10.9.2. There is no physical keyboard attached to the client, as it is virtualized on a VMware ESXi host and has no USB ports available. I'm using the German keyboard layout on server and client; the physical keyboard on the server is a "das keyboard", ISO keyboard type.

As described by Peter, when I press the # key, which is located three keys to the right of the L key in the German layout, I get the character 3. Pressing alt-# gives a pilcrow (U+00B6), which corresponds to alt-3 on the normal German keyboard layout. So I think this is the same behavior that Peter seeing, except that he is using the UK layout rather than the German one.

Observation: On the server, the Keyboard Viewer shows the expected German layout on an ISO keyboard. However, on the client the Keyboard Viewer shows a German layout on an ANSII keyboard. The ANSII keyboard has a wider Return key, so there is no physical key in the location where the # key would appear in the German/ISO layout. The German/ANSII layout has the # key above the Return key in a location that is taken up by the upper half of the Return key in the ISO layout.

I have checked the contents of /Library/Preferences/com.apple.keyboardtype.plist and it appears to be the same on both server and client. (The client was cloned from the server.) I tried to run /System/Library/CoreServices/KeyboardSetupAssistant.app/Contents/MacOS/KeyboardSetupAssistant before and after removing the .plist, but it reports "No unknown keyboard connected - terminating", perhaps because the client has no physical keyboard at all.

So, in short, I suspect the issue may be caused by a keyboard type mismatch between server and client. Is there a workaround?

[nbolton]

• Author: Aaron C
• Date: 2014-05-01 13:27:26

I seem have this same bug too. Started #4031 with more details.

[etothepii]

I can confirm this issue with mac os X.9.5 client with synergy version 1.5.1r2398 and a Ubuntu server (apprently linux 3.1.3)

I am also using uk keyboard

[rbairwell]

I've got the same issue here.

Client: Synergy Premium 1.5.1 running on Linux Mint 16 Petra 64 bit (Mate) kernel 3.11.0-26 Server: Synergy Premium 1.5.1 running on Windows 7 Home Premium Service Pack 1 (Regional settings: English (United Kingdom) - United Kingdom) Keyboard: Razer BlackWidow USB (plugged into server)

When pressing shift and the "at symbol" key - @ - (located two keys to the right of "L" on a key with an apostrophe ' - which works correctly), I expect @ to be generated: instead, on the Linux client, I get Ω .

The @ works correctly on the Windows Server and on Linux if I plug the keyboard directly in.... The @ symbol is quite important for email and twitter ....

[m1ga]

Same issue https://github.com/synergy/synergy/issues/3127#issuecomment-58851403 here with:

OSX Client (1.6.3 nightly) Windows 7 Server (1.6.3 nightly)

[Momodedf]

Hello,

Same issue for MacOS X 10.10.2 as client and Ubuntu 14.04 both using Synergy 1.6.2

[sbnmrk]

Hi,

same issue here with a Gentoo server and Mac OS X 10.10.2 as a client both running Synergy 1.6.2. Keyboard is an Apple Keyboard with german layout that works as expected on the server machine regarding the [#/'] key. On OS X you get [3/`] through Synergy when pressing the same key.

For a programmer the bug is pretty annoying since you need the hash/apostrophe key all the time ... :/

Thanks!

[tripplet]

Hi, same issue here, Windows 8.1 as server & OS X 10.10.2 as client both running synergy 1.6.2 German keyboard on windows PC. I also have problems with other keys I need quite a lot for programming: Pressing the following key's does not result in the desired characters

Alt+5 expected [ got nothing Alt+6 expected ] got nothing Alt+8 expected { got 5 Alt+9 expected } got 6 Shift+# expected ' got `

[SebastianAigner]

Same Issue, I use the German Keyboard Layout on a "Das Keyboard Professional". I guess this really is an issue with ISO/ANSI keyboard detection as @nbolton suggested.

[eljtel]

Are there any workarounds for this issue?

The following characters are also not passed from Mac server to Windows client: §±€

[comes]

any solutions for this problem?

[apolalca]

same bug Mac os client and Ubuntu for server

Alt+5 expected [ got nothing Alt+6 expected ] got nothing Alt+8 expected { got 5 Alt+9 expected } got 6 Shift+# expected ' got `

[joernv]

Same bug here with Windows 7 server and OS X 10.11 client using Synergy 1.8.0-alpha-19835b6 or 1.7.5-rc1 with a german keyboard. This is really annoying an makes Synergy kind of unusable for coding. Any hints for a workaround?

[benbooth493]

Same issue here.

Running server on MacBook Pro and client on Fedora 23. I can't LeftAlt+3 or RightAlt+3 to generate '#' character.

[ManuelRiegler]

I am using Windows 10 as server and OS X El Capitan 10.11.2 as client and this is still a Bug in 1.8.1 beta! -> # on PC prints a 3 on MAC and so on ...

Before I updatet to Windows 10 I had Vista and I used old synergy versions, some thing like 1.3.1, on both machines -> ALL FINE

This bug, which seems to be reported also in some other issues, is dated back to 2014 on several plattforms. This is a show stopper, as you know for sure by yourself, but it seems that it doesn´t get the attention as it deserves.

[jaoord]

While you're there, please also fix #4

[qaisjp]

Pretty sure this is still an issue.

[qaisjp]

With Windows as the server and macOS as the client, my solution to this is to switch the macOS keyboard from "British" to "British - PC". I'm not sure if this is a proper fix though.

[connrs]

Hi folks,

I've come here from #2637 which was marked as a duplicate of this (despite this on being about Win host/Mac guest and 2637 is Mac host/Win guest).

Needless to say I need to report that Mac host/Win guest is still definitely an issue. I'm unable to send # (Alt+3) to a Windows 10 guest from a macOS host running 1.14 stable (or 1.13 or 1.12 for that matter).

However, I am able to do it in reverse. Win 10 host with a macOS client is working. Perhaps this is purely because I've got a UK keyboard layout with a # symbol available as a standard key with no modifiers needed.

macOS 11.4, Host, 1.14 stable, Standard Mac UK keyboard layout on Magic Keyboard Windows 10 Guest 1.14 stable, Standard UK keyboard layout on Microsoft Keyboard

[adamski]

With Windows as the server and macOS as the client, my solution to this is to switch the macOS keyboard from "British" to "British - PC". I'm not sure if this is a proper fix though.

This is the only solution that worked for me!

[comes]

after a couple of years with no response, I switched to logitech flow (https://www.logitech.com/en-us/software/features/flow.html) which works pretty well for my