search

hashicorp / vagrant

Vagrant is a tool for building and distributing development environments.
https://www.vagrantup.com
Other
26.16k stars 4.43k forks source link

Keyboard difference between embedded ssh.exe files on windows #9457

Open rogermartensson opened 6 years ago

rogermartensson commented 6 years ago

Vagrant version

Vagrant 2.0.2

Host operating system

Windows 10 1709

Guest operating system

Ubuntu 16.04

Vagrantfile

No need for a Vagrantfile

Debug output

No debug output

Expected behavior

On Swedish keyboards we have a key named AltGr for which we use to access important characters as '|' (pipe-sign) and $(dollar-sign).

My expected behavior is to be able to use these characters.

Actual behavior

I can't use pipe and dollar-characters.

Steps to reproduce

  1. Install Vagrant
  2. Set up a box
  3. Login in using SSH

References

When looking into it I noticed that there are two different version of ssh.exe installed with vagrant. One in embedded\bin and on in embedded\usr\bin.

When renaming embedded/bin/ssh.exe to something else (to disabled it) it starts work again. I can see in in the logs that it is now using embedded\usr\bin.

I do not have pretty colors but I can use the keyboard fully.

Text from the log file showing the command that works for me. INFO subprocess: Starting process: ["C:\HashiCorp\Vagrant\embedded\usr\bin/ssh.EXE"]

jeffrson commented 6 years ago

FYI - this happens with german keyboard layout as well.

Cito commented 6 years ago

Can confirm the problem and described workaround on Win 10 with Vagrant 2.0.2.

pseb commented 6 years ago

Same here with french keyboard.

filipelenfers commented 6 years ago

Same here on windows 10 with Vagrant 2.0.2 and using a ABNT2 (Brazilian) keyboard, AltGr keys not working.

Jckf commented 6 years ago

This resolved the problem for me as well. We use Vagrant to host a Laravel development environment locally, and the PHP shell included with Laravel is in frequent use. Needless to say, the dollar sign is pretty important.

rogermartensson commented 4 years ago

It's year 2020 and I'm still running on the same computer only on an upgraded Windows (1903) and updated vagrant. I haven't done a new installation of vagrant in a while and I'm not sure if the update only updates files or if it does an uninstall/reinstall.

Anyway. The problem might be solved but I have not verified. Leaving the issue open until I or someone else can verify it.