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

1.11.1 has rendered code on remote linux host unusable #24151

Closed
yamcenutzer opened this issue Apr 6, 2017 · 2 comments
Closed

1.11.1 has rendered code on remote linux host unusable #24151

yamcenutzer opened this issue Apr 6, 2017 · 2 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster

Comments

@yamcenutzer
Copy link

yamcenutzer commented Apr 6, 2017

  • VSCode Version: 1.11.1
  • OS Version: fedora 20, centos 7.3, rhel 7.3

Steps to Reproduce:

  1. install the update
  2. open a file and try to navigate using the arrow keys or the usual navigation keys

arrow keys don't work
if you use the numeric keypad (num lock off) random chars ae inserted into the text
for a c++ file this basically destroyed the text

You do know, that linux machines are usually accessed via a ssh (e.g. putty) and x-forwarding...
The scan codes might not be working there
Please provide a download of 1.10.x as this has rendered everything useless.

@yamcenutzer yamcenutzer changed the title 1.11.1 has rendered linux unusable 1.11.1 has rendered code on remote linux host unusable Apr 6, 2017
@chrmarti
Copy link
Collaborator

chrmarti commented Apr 6, 2017

Which keyboard layout are you using? U.S. English?

@chrmarti chrmarti added the info-needed Issue requires more information from poster label Apr 6, 2017
@alexdima
Copy link
Member

alexdima commented Apr 7, 2017

@yamcenutzer I believe this is a duplicate of #24107

i.e. https://bugs.chromium.org/p/chromium/issues/detail?id=709242

Perhaps you can star the Chromium issue and jump in in case the Chromium team need more information on how to reproduce.

The workaround is: Use the following setting "keyboard.dispatch": "keyCode". Restart VS Code.

@alexdima alexdima closed this as completed Apr 7, 2017
@alexdima alexdima added the *duplicate Issue identified as a duplicate of another issue(s) label Apr 7, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

3 participants