Bug #411 - Ubuntu 10.04 Alpha 3 - Shift gets stuck upon leaving screen
- Duplicates: Bug #18 - Sticky modifier/meta keys (shift, ctrl, alt)
Google user: lwoydziak
What list of steps will reproduce the problem?
1. Start ubuntu machine
2. synergyc is configured with Linux Autostart
4. Type some text (text should be Ok here)
5. Mouse to another computer
6. Return to ubuntu machine
What version of operating system, and Synergy+ are you using?
Windows Vista 64bit + Synergy+ v1.3.4
Ubuntu 10.04 Alpha 3 + Synergy+ v1.3.5
Problem also occurs with Synergy
What is the expected behaviour, and what happens instead?
Expected: Shift key should keep state.
Observed: Shift key gets stuck down (all text/mouse movements are affected)
Is there a way of temporarily working around your problem?
Yes, from the server do a force reconnect.
Would you like to solve the problem yourself and submit a patch?
I would, but I am busy with my day job.
Google user: markjreed
Seeing the same issue with Synergy 1.3.1, so it's not specific to Synergy+. In my
case it's ctrl getting locked instead of shift.
Restarted both server and client, making sure that neither is in capslock or control-
capslock mode. Typing is normal the first time I switch to the Ubuntu host, but
after mousing to Windows and back, everything is control-locked. Toggling the duplex
settings for the Ubuntu client in the synergy config didn't help.
Google user: EliFlesher
I don't think that this was a duplicate as the behavior is not exactly the same. For me, using a Mac Server and Ubuntu Client, all works well until I press the shift key while typing on the client, then the shift key get's "stuck". This is not cleared when moving out of and then back into the screen, the only remedy is to press the client's native shift key (or reconnect the client).
I've run through the synergy+ degug (debug1) log and found that the client registers both an up and down event, whereas when the other control keys (and sometimes shift) get stuck the up event never registers as the focus is taken away from the client before the event.
Google user: EliFlesher
Actually solved this one, sorta.
This behavior occurs when starting Synergy from the command line as the user, command line as root, when started when the GDM starts, when using quicksynergy and nearly every other way I know to start it except the following:
Create the following as a .sh script:
/usr/bin/synergyc -f -n (name) (ip of server)
Add that script to the startup applications in gnome... I don't know why this works, but it does.