Synergy-core: Omega (Ω) symbol appears instead of @ on GB keyboard

[nbolton]

Imported issue:

• Author: nick.bolton.uk (Google user)
• Date: 2009-05-25 00:00:00
• Legacy ID: 71

What steps will reproduce the problem?

1. Client: Ubuntu 9.04
2. Server: Windows Vista SP1
3. Press right shift and the [@ '] key

What is the expected output? What do you see instead?

Expect: @
See: Ω

[nbolton]

• Author: nick.bolton.uk (Google user)
• Date: 2009-10-29 00:00:00

This was previously a duplicate, since fixing issue #google:5 would potentially solve this
issue, however I will make it an issue of it's own since we can maybe use a quick fix
to solve.

[nbolton]

• Author: bob.goddard (Google user)
• Date: 2009-11-10 00:00:00

Latest client version that correctly reproduces the @ is 1.2.2

[nbolton]

• Author: nick.bolton.uk (Google user)
• Date: 2009-11-10 00:00:00

Cool, thanks for the research. Maybe someone could do a diff between the sources to try
and spot when the bug was introduced?

[nbolton]

• Author: simonc591 (Google user)
• Date: 2009-11-17 00:00:00

I see this with the latest synergy-plus 1.3.4 clients both running on Linux (SLED11
server and opensuse11.2 client)

[nbolton]

• Author: nick.bolton.uk (Google user)
• Date: 2009-12-22 00:00:00

Here's a copy of an IRC chat between kodomo and myself...

It is a UTF problem :D
after switching the locale to C (system wide) and rebooting, synergy
produces the correct @
my keyboard settings don't work anymore, I'll have to redo them (actually
I'm lacking the arrow keys and right-ctrl on my laptop keyboard now), but synergy
works like a charm again
I'd recon that synergy works in exactly those cases, when the locales of the
two systems are the same
because I recon that there's no translation done anywhere in the code, is
there?
it probably takes the values and passes them on to the running X, doesn't
it?
hmm, not sure
so you've found a work around?
yes - synchronize the locale settings of the two machines
basically, I realized that the locales setting (visible by typing 'locales',
or looking at - a.o. - the LANG env variables) of the two machines differed
one was LANG=C, the other LANG=en_US.UTF-8 (guess why US stuff works, hehe)

[nbolton]

• Author: [email protected] (Google user)
• Date: 2009-12-23 00:00:00

Not sure how you change locale for windows. I'm not sure we can actually, we can't
even set our own backdrops at work.

[nbolton]

• Author: paul.campbell (Google user)
• Date: 2009-12-24 00:00:00

I managed to get around this by switching the client and server around. ie. using my
linux machine as the server. I realise this may not be possible for everyone but
sorted this out for me.

[nbolton]

• Author: nick.bolton.uk (Google user)
• Date: 2009-12-24 00:00:00

Thanks for the update Paul. This may be helpful to know when we fix the bug.

[nbolton]

• Author: wagooo (Google user)
• Date: 2009-12-27 00:00:00

Not ideal, but try this on the client:

xmodmap -e "keycode 24 = q Q at at at at"

[nbolton]

• Author: jasonirwin73 (Google user)
• Date: 2009-12-28 00:00:00

Yup - that is the workaround. Make sure to add it to your start-up scripts on the
client.

[nbolton]

• Author: nick.bolton.uk (Google user)
• Date: 2010-01-13 00:00:00

According to this SU question:
"http://superuser.com/questions/77734/synergy-linux-keyboard-problem":http://superuser.com/questions/77734/synergy-linux-keyboard-problem

This is the best work around:

xmodmap -e "keycode 53 = x X greater greater greater greater"
xmodmap -e "keycode 52 = z Z less less less less"
xmodmap -e "keycode 24 = q Q at at at at"

[nbolton]

• Author: anton.piatek (Google user)
• Date: 2010-02-09 00:00:00

I have en_GB.UTF-8 on both (linux) boxes but also get this error. The workaround
solves it though

[nbolton]

• Author: jasonirwin73 (Google user)
• Date: 2010-04-01 00:00:00

One thing I have spotted is that, randomly, the problem can re-appear on the client
machine. To get around this I created a script to re-apply the fix and put a
launcher on one of my Gnome panels. It basically does a full restart of ssh and
synergy+ (the retsart of ssh might not be required).

I don't like the killalls in the script, this could be a problem if you are running
more than one ssh session (as it happens, I do not) but hopefully it will be of help
to someone. If anyone knows how to close a specific ssh connection, that would be
great.

#!/bin/bash
#Start ssh
killall ssh
sleep 1
ssh -f -N -L localhost:24800::24800 @

#Start Synergyclient
killall synergyc
sleep 1
synergyc localhost

#Workaround synergy ?/@ key issue
sleep 1
xmodmap -e "keycode 53 = x X greater greater greater greater"
xmodmap -e "keycode 52 = z Z less less less less"
xmodmap -e "keycode 24 = q Q at at at at"

[nbolton]

• Author: Nick Bolton
• Date: 2010-09-04 10:59:00

Found this link in another issue:
http://www.deltanova.co.uk/456/

[nbolton]

• Author: Hans Petter Jansson
• Date: 2010-09-28 17:37:09

Keep in mind that some users also switch keyboard layouts after login - for instance, I use the USA layout for programming, and switch between USA, Norwegian and Spanish layouts when writing mail or IM. I use the GNOME keyboard switcher applet with a hotkey for this, which switches the layout on the host (input devices attached) system.

For the record, I'm seeing these problems with sending non-ASCII letters across Synergy screens too. With version 1.3.4, holding down shift and the key that normally produces the Norwegian letter '', produced a single uppercase '' and then locked up the remote synergyc, which apparently got stuck producing the letter '/' at the maximum speed allowed by the CPU.

[nbolton]

• Author: Tom Russell
• Date: 2011-07-28 17:07:24

I'm experiencing this issue.

Server:

• Arch Linux
• Version 1.3.7 Protocol 1.3
• echo $LANG => en_GB.utf8

Client:

• Ubuntu 10.04
• Version 1.3.4 Protocol 1.3
• echo $LANG => en_GB.UTF-8

Slightly different lang, but the same character set. The xmodmap workaround does work for me though.

[nbolton]

• Author: Nick Bolton
• Date: 2011-10-27 02:06:29

I notice that this only happens when I have caps lock on.

[nbolton]

• Author: Nick Bolton
• Date: 2012-07-25 01:13:48

Still happening in 1.4.9, not sure about my last comment about caps lock -- this doesn't seem to be the case now. Always happens.

[nbolton]

• Author: Asfand Yar Qazi
• Date: 2012-08-25 18:52:15

I can confirm this still happens in 1.4.10 - Windows Vista server + Ubuntu client

[nbolton]

• Author: Paul Green
• Date: 2012-09-26 10:18:07

Server: Ubuntu 12.04: Synergy 1.4.10 LANG=en_GB.UTF-8
1st Client (right): Windows XP Pro SP3: Synergy 1.4.10 Region English (United Kingdom) - @ symbol appears correctly
2nd Client (right again): Ubuntu 12.04: Synergy 1.4.10 LANG=en_GB.UTF-8 - @ appears as ?
I can copy and and paste the @ symbol from the server and 1st client to the 2nd client and can copy and paste the ? from the 2nd client to the server and 1st client.

[nbolton]

• Author: Gabriel Rossetti
• Date: 2012-09-27 13:21:00

I have the same issue, both machines run Ubuntu 12.04, both have Synergy 1.4.9 (1.4.10 doesn't work well (major regression), I have already raised a ticket). Both machines have the same keyboard layout (UK english) and region (US english). This looks like a 3 year old bug, has any work been done on this?

[nbolton]

• Author: Matt Reynolds
• Date: 2012-10-19 16:27:35

I also have this issue, Server XP 1.4.10, client linux 1.4.10 UK / gb language settings.

[nbolton]

• Author: Edwin Grover
• Date: 2012-11-15 11:36:06

Same issue here:

Server: Windows 7
Synergy Version 1.4.10

Client : Ubuntu 12.0.4 LTS
Language variable on Client : en_GB.UTF-8

Seems this issue has been around in some form since 2006. Any chance its going to be fixed. @ sign pretty useful in this day and age.

[nbolton]

• Author: Gabriel Rossetti
• Date: 2013-02-26 08:35:09

Same issue, using 1.4.9 on client and server, both machines are Ubuntu 12.04, setxkbmap -query gives same output on both.

[nbolton]

• Author: Sebastian Jylanki
• Date: 2013-03-11 17:10:46

I have the same issue.
Server: Windows 7, Synergy 1.4.10
Client: Mint Linux 14, Synergy 1.4.11

I have recorded the debug1 output when this error happens:
http://paste.ubuntu.com/5605297/

shift + [' @] sends many extra keystrokes as well it seems...

[nbolton]

• Author: Will Mann
• Date: 2013-03-28 14:26:24

Server: Win 7SP1 Synergy 1.4.10, Mint Linux 1.4.10, same issue, GB Keyboard
Going across keys left to right from to =, then q to ], etc, till /. Seems that [] produces an 8&9 and \ produces , etc. 1234567890-=qwertyuiop89asdfghjkl;'#-zxcvbnm,./
!"$%%^&*()_+QWERTYUIOP{}ASDFGHJKL:q~ZXCVBNMZX?

[nbolton]

• Author: Will Mann
• Date: 2013-03-28 14:44:10

Sorry on my last - that's inside a Windows Remote Desktop environment.

[nbolton]

• Author: Ashley Broadley
• Date: 2013-05-14 12:41:18

I'm also suffering this issue.
Server: Mac OSx 10.6
Client: Ubunutu 12.10

Both client and server are running on 1.4.12

[nbolton]

• Author: Luke Huxley
• Date: 2013-05-16 16:49:48

Is this seriously still an outstanding bug?

[nbolton]

• Author: Massimo Mongardini
• Date: 2013-06-03 16:52:48

This is still an outstanding bug. @ = ? in linux client and mapped as "q" on windows.

[nbolton]

• Author: Trevor Best
• Date: 2013-06-19 17:04:40

Having the same problem, Linux Mint Client and Windows 7 server. The modmap commands work and produce the correct @ in the Linux box but when using VirtualBox on the Linux box, the same key combination wants to close the VM. As though it sent AltGr + Q. Normally pressing AltGr does nothing so I have to reach over to the laptop and press it on that keyboard, which is what I'm currently having to do to get the @ symbol in a VM. No fun when writing SQL queries with lots of variables as they all begin with "@".

[nbolton]

• Author: Jonathan Websdale
• Date: 2013-11-06 15:43:23

This is still an outstanding bug. @ = ? Server: Windows 7 Ultimate 64-bit running Synergy 1.4.15 and client is Ubuntu 12.0.4 LTS running Synergy 1.4.15.

[nbolton]

• Author: Keith Patton
• Date: 2013-11-07 15:23:49

I can confirm this is still an issue. Just installed/configures synergy for the first time:

Server
Arch Linux 64bit
synergy 1.4.15-1
UK keymap
locale: LANG=en_GB.utf8

Client
Debian 3.2.51-1 i686
synergy 1.3.8-2
UK keymap
locale: LANG=en_GB.utf8

[nbolton]

• Author: Oliver Corbett
• Date: 2013-12-11 14:10:12

Server: Windows 7

Client: Linux Mint 16

I'm using an Apple keyboard on the server machine (Windows 7) and changing the keyboard layout on the client from "English (UK)" to "English (Macintosh)" resolved the issue for me.

[nbolton]

• Author: Andy S
• Date: 2014-04-11 17:34:37

Both the Linux Mint 16 server and Debian Jessie/Sid client have the same en_GB.utf-8 settings and I too get a ? when I hit the @ key both using latest ver from your site...

I'd be more inclined to contribute financially to a great and useful project like this if bugs like this got resolved in a more timely fashion!

[nbolton]

• Author: David Kelly
• Date: 2014-04-24 10:34:43

Nick Bolton advised to update a set of issues upon the issue tracker, as of Thursday 24th April 2014.

ISSUE:-
The "?" character appearing in the stead of the "@" character, the issue remains on your issue tracker for a number of years, so why has it not been fixed, as an accepted issue upon the issue tracker, as Bug#71 open since 25 May 2009, seems not to have been assigned to anyone, so has remained unresolved? From:-
From Old issues list:-
https://code.google.com/p/synergy-plus/issues/detail?id=62
Now migrated to new issues list as a current set - note the issue still active
http://synergy-foss.org/spit/issues/details/71/
"...
Bug #71 - Omega (?) symbol appears instead of @ on GB keyboard
Status: Accepted
Priority: Normal
Assignee: None
Created on: 25 May 2009
...".

CONFIG:-
Windows 7, 32bit, with service pack1 all updated as of 24th April 2014, running Synergy server 1.4.16. Note this is the latest version that would work with the Ubuntu Synergy 1.4.17.
Ubuntu 12.04LTS, 32bit fully uptodate as of 24th April 2014, running Synergy client 1.4.17.

OTHER ASSOCIATED ISSUES, raised to Synergy via email to Nick Bolton:-
Nick Bolton - Project Leader,

RE: 23rd April 2014, Some updates and a request for support please,
Nick and all at Synergy; thanks for a great product.

OK, so I have been testing the Synergy product for a month or so now,
and first impressions are of an easy to use product, that has a
journey to go to improve and add new features.

Issues:-
(01) Upon startup upon windows, there is a DOS style CMD box that pops
up and does not go away unless the program windows is closed.
(02) Ubuntu startup requires login before the Synergy client kicks in
to startup, as such requires a keyboard to login. I have a
screen/keyboard switcher that I suppose I could use as a virtual
keyboard, but due to the development platform it is easier to have a
keyboard stashed to the side. Could Synergy be changed to start and be
used at the Ubuntu login screen or before.
(03) The control programs look to run in the background, and when the
GUI front ends are run, the programs interpret them as secondary
duplicate programs, that do not control the operation of the
server/client.
(04) It is not clear what the "elevate"setting is for, but the program
does not seem to work as the windows server unless the setting is set.
(05) The windows server window does not minimise to the desktop
notifications area, instead the window is just minimised, along with
other standard windows, that is not the normal operation of a program
that operates as a program reduced to the notifications area, in the
task bar.
(06) When locking the Windows 7 server, the Ubuntu client locks
retaining control of the cursor, meaning I cannot unlock the Windows 7
server.
(07) Ubuntu swapping screens triggers a screen flash, by which looks
to do a hardware screen refresh, with the consequence of
jitters/flashes upon the screen, like the issues of old with screen
refresh synchronisation in the old technology.
(08) Copy/Paste works intermittently. ....ongoing issues win7
clipboards......!!!! just had a Chinese language past out of nowhere.
It seems there are different operations for paste, from the control
keys copy "ctr-C" to paste "ctr-V", and the different copy/paste
method using the programs main menu, as in word processing or such,
edit, then copy/paste.
(09) The current version of Ubuntu client 1.4.17 would only work with
the older version of the Windows Synergy server 1.4.16, and not the
later version 1.4.17.

[nbolton]

• Author: Alex Potter
• Date: 2014-08-18 10:02:40

Still not fixed in 1.5.0. Ubuntu 14.04.1 on server and clients.

[nbolton]

• Author: Mark Phipps
• Date: 2014-08-29 20:47:22

Please fix this. I respond to your donation requests and have donated various times. To not have an AT symbol but an ? instead after 5 years of knowing of this problem is kinda unacceptable - so I will not be donating any more until this issue is fixed. Sorry Nick.

[nbolton]

• Author: Luke Huxley
• Date: 2014-09-04 10:54:08

I'm surprised this is still a problem, I thought downloading the latest version of Synergy after a few years of not using it would have sorted this by now. But I'm still implementing a workaround that I had to do years ago to get my keyboard mapping correctly. Synergy, you should be ashamed of yourselves.

[nbolton]

• Author: Juan Pablo Caivano
• Date: 2014-09-30 14:55:19

Same problem here, using elementaryOS at both, server and client side.

[pcp16]

Same problem here!! the xmodmap fix worked but this should be solved in the Synergy code:

the fix was to run:
$ xmodmap -e "keycode 24 = q Q at at at at"

(only works if the client is a Unix, I presume).

[chrisjrob]

Same problem with omega instead of at sign.

Fresh installation of synergy 1.6.2 downloaded from synergy website last week.

• Server: Windows 8.1 Pro - English UK Locale
• Client Ubuntu 14.04 en_GB.UTF-8

xmodmap fix works fine.

[matthewbloch]

FWIW, this happened on the last nightly build for me (Debian/jessie client, Windows server), and the xmodmap fix worked.

[the-wes]

See also https://github.com/synergy/synergy/issues/4352

[ivebeenlinuxed]

I won't be "buying" synergy while this bug is around.

[mwelchuk]

Seeing this bug on Debian Jessie (as both client and server).
Both machines have LANG=en_GB.UTF-8.
Both are amd64 (x86_64).
Both are running version 1.4.16-1.

[Lanvar]

I am experiencing the same problem, server is a windows 7 (64bit) system and the client is a Linux Mint (17.2) box. Extremely frustrating.

Any word of a fix on this bug yet? It has been open over a year....

[nosnickid]

I'd also love a fix. Seems like it's been open over 6 years...

"
Imported issue:

Author: nick.bolton.uk (Google user)
Date: 2009-05-25 00:00:00
"

[ivebeenlinuxed]

I find it very annoying that this bug is not fixed, yet there is talk about adding "serial keys" in in the next milestone. All I've seen in these milestones is "flashy features", without any graft fixing existing bugs.

Maybe I should start packaging Synergy myself for my business needs... I've offered money and that didn't work...

[wrapper]

Here to add a +1 to needing a fix for this

[bobdvb]

+1 to having just run into this.

Server: Windows 7
Client: Ubuntu 14.04 configured to enGB.UTF-8

Interestingly when I copied the xmodmap to the clipboard it caused the Linux machine to log out!?

[kjbweb]

+1 same here

Server Windows 7
Client: Linux Mint 17.2

A 6 year old bug! Wow... :-/

[StreetGuru]

Ticking "Use System keyboard layout" in Advanced settings of the "Ibus Preferences" has solved the problem for me.

[prabjohns-atex]

Same bug for for me... @ becomes Omega. Server = OSX EL Capitan (with British PC keyboard), Client = Ubuntu
(Paid up Donater to Synergy)

ps. the xmodmap fix works for me too.

[rrthomas]

Sounds good; however, I'm using uim, not iBus, and see no similar option in its prefs.

[dannystaple]

I'm still reproducing this.
Server: Windows 8 with British Laptop keyboard
Client: Fedora 23 with UK Keyboard configured.
Versions: Synergy Pro 1.7.6 at both ends.
The Xmodmap workaround appears to work for now.

[niczero]

The stated workaround used to work for me, and then it stopped working. If you are one of the many casualties who are seeing omega rather than at, and you're using UTF, the workaround is as follows.

1. Check that the client's locale is as compatible as possible with the server.

locale

1. Get the current settings of your xmodmap.

xmodmap -pke | grep -w 24

1. Write a client startup script that sets the keyboard and modifies the sequence from #2. (You probably only need to replace the one 'omega' value with 'at'.)

synergyc --daemon $SERVER_IP &>>/var/tmp/synergy.log setxkbmap gb xmodmap -e 'keycode 24 = q Q q Q at at at'

The key message is that the number of values you set must match the number previously set, or you will see silent failure.

[nbolton]

@XinyuHou @nlyan We should solve this bug soon.

[XinyuHou]

This was previously reported in issue #62 a couple years ago (#62)

The workaround within the issue works great for me to get around this but, I have pasted it below for your convenience. I guess you can try changing the symbol in the script if you have issues with other symbols for other keys such as "\" or "/" or "|".

For reference I'm running 08th August's Nightly build. Server is Win 10 and client is Ubuntu 16.04.

!/bin/bash

Start ssh

killall ssh

sleep 1

ssh -f -N -L localhost:24800::24800 @

Start Synergyclient

killall synergyc

sleep 1

synergyc localhost

Workaround synergy ?/@ key issue

sleep 1

xmodmap -e "keycode 53 = x X greater greater greater greater"

xmodmap -e "keycode 52 = z Z less less less less"

xmodmap -e "keycode 24 = q Q at at at at"

[brunovianarezende]

I just tested with ubuntu 14.04 server (brazilian keyboard) and client (GB keyboard). This problem doesn't happen anymore.

[nlyan]

@brunovianarezende What Synergy version did you test with?

[brunovianarezende]

version 1.8.3 both in client and server.

[nlyan]

I'm closing this as fixed in 1.8.3. If anyone still has this, or a similar, problem after this version please open a new issue.