We just pushed out a significant update that should fix a number of keyboard issues on Mac, Windows and Linux! You should get auto-updated, but if not:
Mac/Windows: Settings > scroll down to see if there’s an update
Linux: snap refresh screen or update via Debian
If something doesn’t work, please comment below with the following information:
1) OS & keyboard language of the screen share host
2) OS & keyboard language of the screen share guest
3) Key combination pressed (e.g. Opt-Shift-2)
4) Expected outcome (e.g. €)
5) Actual outcome (e.g. @)
Thanks!
This one is the other way around:
1) Windows 10, Japanese keyboard
2) Windows 10, US keyboard
3)
`-=[]\;',./
Shift and `1234567890-=[]\;',./
4)
`-=[]\;',./
~!@#$%^&*()_+{}|:"<>?
5)
@--[]\;7,./
~!`#$%~&*()_+{}|*"<>?
The attached photo is the physical US keyboard of the guest.
This is less important than the Kanji key issue (see below) but anyway:
1) Windows 10, US keyboard
2) Windows 10, Japanese keyboard
3)
-^\@[;:],./\
Shift and 1234567890-^\@[;:],./\
4)
-^\@[;:],./\
!"#$%&'() =~|`{+*}<>?_
5)
-6\2[;;],./\
!"#$%&"() +~|~{+*}<>?_
Above, the spaces after ")" mean "no output at all".
See the attached photo for the physical Japanese keyboard of the guest.
1) Windows 10 (latest update) and Japanese keyboard
2) same
3) the "Kanji" key (left to "1" in https://en.wikipedia.org/wiki/Japanese_input_method#/media/File:Surface_type_cover_JIS_keyboard_layout_blue.jpg )
4) Toggling the IME mode (default on Japanese Windows, though it can be changed and worked around)
5) nothing happens at all
Hello, I try to use screen.so to join from mac os to windows. When I type any symbols from mac on the remote machine I get only numbers and special symbols. Looks like layers are mismatch. I tried to change input languages. The problem still persists.
Could you please give details on:
1) OS & keyboard language of the screen share host
2) OS & keyboard language of the screen share guest
3) Key combination pressed (e.g. Alt-Shift-2)
4) Expected outcome (e.g. €)
5) Actual outcome (e.g. @)
Win -> Mac the same.
I'm running v1.0.68 | v1.0.22 on Ubuntu installed through snap
I just witnessed an issue, where they keyboard layout was the one of the host and not my layout. The host was using a Swiss keyboard layout while I use the American layout.
Later in the call, keyboard input would not work at all even though I could still click around with my mouse. Don't know what other details I can share as there was nothing exceptional happening.
Let me know if I can provide more details.
@Ken B: were both host and guest on Ubuntu (which version)? And both on the same version of Screen?
@J Sherwani (Screen Team): Both the host and guest were running Ubuntu 18.04. I don't know which version of Screen the host was running, but given they installed in the last couple days, I would bet it's recent.
@J Sherwani (Screen Team): Thanks for the update! We just updated both the Linux version of Screen and Mac version of screen and now the shift key on my Mac isn't working at all for any characters. Previously it worked for all except double quotes, but now its not working for any.
1) OS & keyboard language of the screen share host
Host Linux: Ubuntu 18.04.3 LTS
2) OS & keyboard language of the screen share guest
Guest Mac: macOS Catalina 10.15.3
3) Key combination pressed (e.g. Opt-Shift-2)
Shift+anything
4) Expected outcome (e.g. €)
Shift+typed key, e.g. !@#$%^
5) Actual outcome (e.g. @)
Key without shift: 123456
The only keys that the shift key is working for now is the "," which correctly changes to "<" and numbers 9 and 0 for '(' and ')' respectively. No other keys work on the guest Mac with the shift key.
@Derek Lee Boire: You’re right, sorry about that (we’re going to create automated tests to ensure we test all combinations of OSes, but for now we’re doing it manually). Will fix right now!
@J Sherwani (Screen Team): No worries, thanks for your prompt support! Happy to provide more info if there's anything else that you need. All the best, Derek
@Derek Lee Boire: I just pushed out a fix for this (client v1.0.60, app is still v1.0.19), which is now live. I can confirm the bug you pointed out has been fixed. We’re also now working on cross-platform automated tests which should improve the quality of our keyboard mapping feature considerably.
@J Sherwani (Screen Team): Thanks for providing a quick fix for this! I can confirm based on the above configuration that the shift key is now working with (from what I can tell) all keys on my US-layout keyboard.
However, the ALT key, which was working previously, is now not working in any case that I can tell. Update: Alt+Enter is working in IntelliJ, but I can't seem to get any other ALT+ keyboard shortcuts to work.
(Configuration is the same as above.) Let me know if you need me to provide any additional information. Thanks!
@Derek Lee Boire: Amazing find! I just pushed an update (now live) which addresses this. Now:
• when you connect from a Mac to a Mac, the alt/opt key will send the modified key, e.g. opt-f will end ƒ
• when you connect from a Mac to a non-Mac, it will send the unmodified key, e.g. opt-f will send alt-f
Let me know if you find any other issues, and thank you so much for your incredible attention to detail! 🙌
@J Sherwani (Screen Team): Thanks to you (and your team (?)) for providing the service! We are pairing with clients for the next few weeks (Mac -> Linux) so I will continue to share feedback with you to let you know how it goes. Just wrapped up for the day so we will update and give it a go tomorrow. Thank you so much for your great support! It's helping us be able to get our work done since we can't pair in person. Really appreciate it!
@J Sherwani (Screen Team): Another datapoint here. The SHIFT modifier for me was broken in an earlier pairing session, but I believe restarting Screen (assuming it auto-updated) resolved it when testing again. Currently on 1.0.21
@J Sherwani (Screen Team) We had a great pairing day today (Mac/Linux) and I was thrilled that all of my keystrokes were functioning! We will continue pairing with Screen and I'll send along any other scenarios if they come up. Thanks again for your great support!
@Derek Lee Boire: Excellent!
@Kevin Gao: Sounds like the issue is fixed — if any other issues come up, please post them here!
@J Sherwani (Screen Team): Had one more come up recently. Same configuration as mentioned previously (host is Linux, I'm on Mac).
I'm using an external keyboard (full size) and the delete key (not the backspace key) types a lowercase letter 'l' (L) when pressed. Not a huge inconvenience, but just passing along. Likely low priority compared to other tasks you're working on. Thanks!
@Derek Lee Boire: This should now be fixed in the latest release!
@J Sherwani (Screen Team): Just tested it out and confirmed! Thank you!!
@J Sherwani (Screen Team) I have a new key request for you to take a look at if/when you have a moment. I believe the "Insert" key on my side (Mac) is not registering on the client host Linux machine. Thanks for your support!
@Derek Lee Boire: I tried to look into this but I don’t have a full keyboard to test with (and my software emulation seems to have led me to a dead end). Is this a blocker for you or do you have a workaround that isn’t too onerous?
@J Sherwani (Screen Team): Not a blocker - low priority. Thanks for following up!