summary refs log tree commit diff stats
path: root/results/classifier/118/none/1831362
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/118/none/1831362')
-rw-r--r--results/classifier/118/none/183136266
1 files changed, 66 insertions, 0 deletions
diff --git a/results/classifier/118/none/1831362 b/results/classifier/118/none/1831362
new file mode 100644
index 000000000..ec6cfa043
--- /dev/null
+++ b/results/classifier/118/none/1831362
@@ -0,0 +1,66 @@
+device: 0.752
+graphic: 0.672
+ppc: 0.660
+virtual: 0.476
+vnc: 0.442
+architecture: 0.381
+peripherals: 0.348
+mistranslation: 0.335
+performance: 0.335
+arm: 0.319
+semantic: 0.316
+socket: 0.262
+kernel: 0.243
+x86: 0.219
+network: 0.184
+boot: 0.179
+PID: 0.167
+i386: 0.158
+TCG: 0.155
+permissions: 0.137
+VMM: 0.125
+risc-v: 0.120
+register: 0.106
+hypervisor: 0.098
+debug: 0.088
+assembly: 0.082
+files: 0.050
+KVM: 0.032
+user-level: 0.025
+
+European keyboard PC-105 deadkey
+
+With a freshly compiled version of qemu 4.0.50 on Windows 10 (host)
+
+I am using 3 different Belgian keyboards and I have the same behaviour
+- 2 USB keyboards (Logitech and HP) and
+- the keyboard of my laptop (HP)
+
+3 characters on the same key cannot be used (the key seams to be dead):
+< (less than),
+> (greater than) used with the combination of LShift or RShift
+\ (backslash) used with the combination of AltGr
+
+Using grub command mode from an archlinux installation (5.1.4)
+The keyboard seams to be a mix of azerty and qwerty keyboard
+all letters are correctly mapped but all numbers and special
+characters are not
+
+Using sendkey in monitor
+"sendkey <" results in : \
+"sendkey shift-<" results in : |
+"sendkey ctrl-alt-<" results in : nothing
+
+REM: VirtualBox can handle this key and with the showkey command
+     from the archlinux kbd package, it shows :
+     keycode 86 press
+     keycode 86 release
+
+
+This is an automated cleanup. This bug report has been moved to QEMU's
+new bug tracker on gitlab.com and thus gets marked as 'expired' now.
+Please continue with the discussion here:
+
+ https://gitlab.com/qemu-project/qemu/-/issues/174
+
+