Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] OSM SHIFT sometimes behaves incorrectly (oryx, moonlander) (RDP related) #15134

Open
urza opened this issue Nov 12, 2021 · 4 comments
Open

Comments

@urza
Copy link

urza commented Nov 12, 2021

One of thumb keys on my Moonlander is configured as one shot shift modifier (and nothing else).
Occasionally it doesn't produce shifted next letter but regular lowercase letter.
The problem is not in timing. This happens when the osm shift key is pressed and released withing the tapping term so should produce shifted character.

I created simple debugging app that prints keyUp and keyDown events and prints them with timestamp (second.milliseconds).
On screenshot below you can see that few times osm shift worked as expected, but then one time it produced lower character because keyboard sent:

shift down
shift up
X down
shift up
X up

The first shift up seems like bug?

image

System Information

  • Keyboard:
    Moonlander mk I, configured with oryx online, flashed with Wally, my tapping term is set to 300 ms so this is not caused by holding the shift too long on the contraty this seems to happen when I press the button very swiftly

  • Operating system:
    Windows 10

  • Any keyboard related software installed?
    No

@urza
Copy link
Author

urza commented Nov 13, 2021

I did some more testing and it seems that something strange is going on. I work mostly remote via RDP (remote desktop from windows 10 to another windows 10), this is where the osm shift is sometimes failing, I would say the rate of failing to produce osm shift is 1 in 10. It happens when the osm shift key is pressed very swiftly for as short period as possible between key down and key up.
However on my local computer, the failure doesn't seem to be happening.

I didn't think RDP could play a role since the keyboard should send key events to local OS and that should be just forwarded to remote OS as is.
But googling this and it seems that this may indeed be RDP issue:
https://superuser.com/questions/219461/shift-and-control-keys-out-of-sync-with-normal-keys-over-rdp

I wonder if anyone encountered similar issue with RDP?

@urza
Copy link
Author

urza commented Nov 13, 2021

Related issue #1037

@urza urza changed the title [Bug] OSM SHIFT sometimes behaves incorrectly (oryx, moonlander) [Bug] OSM SHIFT sometimes behaves incorrectly (oryx, moonlander) (RDP related) Nov 16, 2021
@drashna
Copy link
Member

drashna commented Nov 19, 2021

Yup, that's a known issue. And there isn't a simple fix for it, IIRC

@TartCodes
Copy link

I did some more testing and it seems that something strange is going on. I work mostly remote via RDP (remote desktop from windows 10 to another windows 10), this is where the osm shift is sometimes failing, I would say the rate of failing to produce osm shift is 1 in 10. It happens when the osm shift key is pressed very swiftly for as short period as possible between key down and key up. However on my local computer, the failure doesn't seem to be happening.

I didn't think RDP could play a role since the keyboard should send key events to local OS and that should be just forwarded to remote OS as is. But googling this and it seems that this may indeed be RDP issue: https://superuser.com/questions/219461/shift-and-control-keys-out-of-sync-with-normal-keys-over-rdp

I wonder if anyone encountered similar issue with RDP?

Hi there!

not sure you will see this but I am having this same issue when I RDP. It;s kinda of a killer because I bought this KB for work purposes, but the layer almost never works and is really ruining my productivity - has there been a fix or a workaround?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants