summary refs log tree commit diff stats
path: root/gitlab/issues_text/target_missing/host_missing/accel_missing/1875
diff options
context:
space:
mode:
Diffstat (limited to 'gitlab/issues_text/target_missing/host_missing/accel_missing/1875')
-rw-r--r--gitlab/issues_text/target_missing/host_missing/accel_missing/18759
1 files changed, 9 insertions, 0 deletions
diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1875 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1875
new file mode 100644
index 000000000..a24f5921a
--- /dev/null
+++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1875
@@ -0,0 +1,9 @@
+qemu-system-x86_64: warning: no scancode found for keysym 65483
+Description of problem:
+qemu-system-x86_64: warning: no scancode found for keysym 65483
+
+I'm hoping this is something that could easily be added to qemu, rather than a limitation of windows:
+
+I want to bind F14 to an arbitrary key, in this case `keycode 148 = XF86Calculator`, but it's not happening, and qemu is giving the error: `qemu-system-x86_64: warning: no scancode found for keysym 65483`
+
+`xmodmap -e "keycode 148 = F14 F14 F14 F14 F14"` Executes with no error, and xev correctly shows as F14 pressed/released, but a windows 10 VM started afterwards cannot recognise this bind.