Synergy-core: Wrong characters typed on client with Russian layout

Created on 19 Jun 2018  Â·  16Comments  Â·  Source: symless/synergy-core

I've got an issue where whenever I try to type in Russian I get "????" instead. This issue is there if I use Windows as host and Windows as client.

Using Linux as Host and Windows as client - no problem, works fine.

But there's another problem, where some programs, like 3ds max, crash or hang often on the client if I have 'ru' on the host and 'en' on the client, and try to use any hotkeys. If I have 'us\en' on both host and client it seems to be working fine.

Latest 1.x stable (1.9.1 ?)

bug

All 16 comments

If you change your layout to US on the client, does it type correct characters?

Here's what's going on. Using Windows Host and Windows Client:

Host ENG - Client ENG - Works fine ( no problem with ASCII\latin chars)
Host RUS - Client ENG - All characters are "????". Numbers work fine. Some special characters ( like â„– which is available in RUS layout on number 3 button) are also represented as ?. Basically any unicode characters seem to be represented as "?".
Host RUS - Client RUS - same thing

Changing layout on Client also forces change on Host when mouse is moved back.

Host RUS - Client change to ENG, if I start typing on client - host is also force d into ENG, and seems to work fine, since ENG+ENG works.

Both systems have US layout as default, and Russian Cyrillic as secondary.


Linux seems to be working fine though, I can type in RUS, but I can't use Mouse Back\Forward keys with Linux as a host. Back\Forward keys work ok with Windows host.

Thanks for the info, we plan to improve international keyboard support.

Do you think that 3ds max crashes (only if RU layout is used) are related to this issue? I mean obviously it's not the case with a keyboard directly attached to a PC :)

@Nixellion you should report it in following issue which grabs together all KBD layoout problems: #6005

@LeadManPL Thanks for the tip. I see you already linked the issue, should I copy my post there as well or is linking it enough?

@Nixellion I have no clue, I'm just client of Symless. Ask @nbolton

Thanks for the info, we plan to improve international keyboard support.

@nbolton Do you have an estimate on when this will be fixed? I've seen multiple threads on this issue from years ago (like this one) and it's ongoing.

@ceco987 we are currently wrapping up the release of Synergy 1.13.0, and then we'll start to work on these issues with international keyboards and characters.

@andreacndn I'm happy to hear that this issue is already addressed and hopefully will be fixed in the next version. Do you have an estimate on when 1.13.0 will be released? Thank you!

We are planning to publish the release candidate 2 this week, likely on Slack and Discord, and depending on how the RC2 goes we'll plan the stable release in the following days.

We are planning to publish the release candidate 2 this week, likely on Slack and Discord, and depending on how the RC2 goes we'll plan the stable release in the following days.

Amazing. Thank you for your time and support, may you and the whole team have a great week ahead! 😊

@andreacndn Hi, I'm currently using the most recent stable version (1.13.1.41) but the issue still persists. Any estimates on when this will be fixed? Thanks.

@nbolton Hi, can you please support us here regarding this issue? @andreacndn replied last on this topic, but his activity dropped. The issue is still present and has been for many years now. Are there any plans to get this fixed? Thank you.

@ceco987 We are actively working on this issue, but we can't provide an estimate for its availability yet.

@andreacndn Thank you for your feedback, I hope it can be fixed at all, as it appears as a highly challenging case, being addressed first around 2014. Meanwhile, I'll keep developing my skills and maybe I'll join the effort for fixing the bug, once I have the needed knowledge.

Have a nice and productive rest of the week!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

bigbear3001 picture bigbear3001  Â·  4Comments

jenelcohen picture jenelcohen  Â·  4Comments

legonigel picture legonigel  Â·  4Comments

jasonosei picture jasonosei  Â·  3Comments

laur89 picture laur89  Â·  5Comments