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

recognize super key for Linux guests, virtualbox builders #5682

Closed
mcandre opened this issue Dec 8, 2017 · 3 comments
Closed

recognize super key for Linux guests, virtualbox builders #5682

mcandre opened this issue Dec 8, 2017 · 3 comments
Assignees

Comments

@mcandre
Copy link

mcandre commented Dec 8, 2017

Similar to #5681 , I wish packer would recognize the Super/Windows key when building VirtualBox VM's.

I think the Left Super scancode is 133, and Right Super scancode is 134, based on StackExchange. The Arch wiki also details how to verify scancode tables with xev, from a working X11 environment.

As the Super scancode is not listed among the Linux keyboard scancodes documentation referenced by the VirtualBox builder source code, I can't guarantee that this scancode would also work for the Super AKA Windows key for Windows guests. Worth experimenting to find out.

I would bet, however, that these scancodes probably do NOT match for macOS guests, as macOS uses a completely different scancode table than Linux/PC/IBM scancodes. #5635 addresses that. In any case, it would be fantastic if packer could finally submit the all important Super key for VirtualBox builds, even if only for Linux and/or Windows guests!

@kikitux kikitux self-assigned this Jan 4, 2018
@kikitux
Copy link
Collaborator

kikitux commented Jan 8, 2018

PR welcome

@mwhooker
Copy link
Contributor

closing assuming this was fixed in #6067

@ghost
Copy link

ghost commented Apr 1, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants