You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when using the vfkit console (started on my case by podman machine start --log-level DEBUG) the keyboard is using english keyboard layout (but keyboard is using for example a french layout)
when using qemu console started by podman machine start as well, it was able to find/use my local keyboard layout
I would expect to have vfkit behaving the same way
vfkit console if I enter azerty on a french keyboard, it displays qwerty
qemu console, it displays azerty as expected
The text was updated successfully, but these errors were encountered:
The vfkit console used by podman is displaying the VM graphical framebuffer, and this behaves as if your keyboard was physically plugged into the VM. This means it honors the keyboard settings configured in the guest, which will be QWERTY by default.
I don't know what the qemu console is, but I'd guess this is using -display curses, the keyboard mapping would be done using the host configuration, and thus would be right in your case.
Once #48 is implemented and podman-desktop supports it, this should give you the behaviour you want.
There is not much vfkit can do for the --gui keyboard behaviour.
when using the vfkit console (started on my case by podman machine start --log-level DEBUG) the keyboard is using english keyboard layout (but keyboard is using for example a french layout)
when using qemu console started by podman machine start as well, it was able to find/use my local keyboard layout
I would expect to have vfkit behaving the same way
vfkit console if I enter
![image](https://private-user-images.githubusercontent.com/436777/300777887-58bf6f52-cd19-49da-b5b0-35b4eda74c53.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk1NDQ2NDAsIm5iZiI6MTczOTU0NDM0MCwicGF0aCI6Ii80MzY3NzcvMzAwNzc3ODg3LTU4YmY2ZjUyLWNkMTktNDlkYS1iNWIwLTM1YjRlZGE3NGM1My5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjE0JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxNFQxNDQ1NDBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iYzJmODgzMDU3NWEyMTI4NGIxZjUzODA0YzExZDk5YjNkOTY4ZTkyYzdmMTJjNThjM2IxOGI4Yjk4NjljM2YxJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.y4wOwVdJn2OGRL_0EjljtlYGOJDrKrtwBaYJl44otuM)
azerty
on a french keyboard, it displaysqwerty
qemu console, it displays
![image](https://private-user-images.githubusercontent.com/436777/300773874-ead2d597-0175-4bae-aaae-1dbd1a8ae503.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk1NDQ2NDAsIm5iZiI6MTczOTU0NDM0MCwicGF0aCI6Ii80MzY3NzcvMzAwNzczODc0LWVhZDJkNTk3LTAxNzUtNGJhZS1hYWFlLTFkYmQxYThhZTUwMy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjE0JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxNFQxNDQ1NDBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT05YTI1MzI5NmUzNjAwZDc3NmUwMzcwZjNjNjllOTQ3NzBiMmFhMjUwYjA0Y2Q4ODEwNTZmZThiYmQ0NDlhNGYzJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.1js4g3i7aLXLEk9qFlwRqXmiv39XueY2uM1hjrvnW7o)
azerty
as expectedThe text was updated successfully, but these errors were encountered: