Bug #21 - Keyboard input is not permited and you receive beeps on any keystroke
- Duplicates: Bug #18 - Sticky modifier/meta keys (shift, ctrl, alt)
Google user: sorin.sbarnea
On Windows as server Mac as client. From time to time you'll see that
you'll not be able to use the keyboard and you'll receive beeps on every
stroke.
What is the expected output? What do you see instead?
Workaround: drag the mouse to the other computer and back. Repeat if needed.
#1
Google user: stag.stag.stag
I think this might be identical to issue #0 that I raised -
"http://code.google.com/p/synergy-plus/issues/detail?id=12":http://code.google.com/p/synergy-plus/issues/detail?id=12
I forgot to mention in my bug report that the client is a Mac, although the problem
occurs on the Windows server too.
The problem appears to be that a computer believes a key such as ctrl or alt is being
held down. Rather than dragging the mouse back and forth, could you try pressing each
of your meta-keys and then try typing?
On the Mac, depending upon which key it thinks is being pressed this problem can
manifest itself as a beep when you type or a right-click being registered when you
left-click.
#2
Google user: sorin.sbarnea
I upgrade the priority on this issue to critical - first we need a test case that
would always reproduce the bug.
Can someone help with that?
#3
Google user: sorin.sbarnea
I think I found a hint on this, at my computer the key getting stuck is RIGHT ALT but
I (think) I never use it. Pressing the key again does release it but is very annoying.
The first workaround form the report doesn't work always.
#5
Google user: malvineous
This looks like a duplicate of issue #9 .
#6
Google user: edw...@carrel.org
This is a duplicate of issue #9 .
@nick, if you are listening on this issue, can you mark this as a duplicate of issue
9, so we don't run the risk of cross-talk between the tickets.
#8
Google user: nick.bolton.uk
Amer, you just beat me to it ;)
Are you guys sure this is a duplicate? I'm probably not reading between the lines here,
but it seems that issue #9 refers to meta keys remaining pressed down. Where as this
issue seems to refer to key strokes being received, but being directed to the wrong
application... Please could someone let me know otherwise if this isn't the case.
#9
Google user: nick.bolton.uk
I just re-read Sorin's 2nd message, and I see that he's referring to meta keys, in
which case I think this is a duplicate if issue #9 . The issue I'm thinking of has not
been reported yet by the looks of it, so I've created issue #2 .
Write comment