diff options
Diffstat (limited to 'results/classifier/deepseek-2/reasoning/graphic/1718719')
| -rw-r--r-- | results/classifier/deepseek-2/reasoning/graphic/1718719 | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/results/classifier/deepseek-2/reasoning/graphic/1718719 b/results/classifier/deepseek-2/reasoning/graphic/1718719 new file mode 100644 index 000000000..781c28c1c --- /dev/null +++ b/results/classifier/deepseek-2/reasoning/graphic/1718719 @@ -0,0 +1,19 @@ +<think> +Okay, so I need to classify this bug report for QEMU into one of the given categories. Let me read through the problem again. + +The user is reporting that QEMU can't capture keys properly under Wayland. They mentioned that many keys work fine but specifically the arrow keys aren't working during boot when using Esc to get to the menu. The error message mentions unknown keycodes '(unnamed)', which suggests something's wrong with how the keyboard input is being handled. + +They're using qemu-system-x86 version 1:2.10+dfsg-0ubuntu1. It works correctly when using Virt-manager, which I think uses SPICE, and also when switching to Xorg instead of Wayland. + +Now, looking at the possible categories: mistranslation, assembly, other, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor. + +The issue is about key capture under Wayland. So it's related to input handling in the graphical environment. The error occurs during boot when interacting with the menu, which might tie into how QEMU handles keyboard events, especially under Wayland compared to Xorg or Virt-manager. + +I'm thinking 'graphic' because it's related to the display and input handling within the graphical interface. Alternatively, 'peripherals' could be a fit since keyboards are peripherals, but the problem is more about how the input is captured in the graphic environment rather than the hardware itself. + +But looking at other examples, issues with key capture under Wayland might fall under 'graphic' or maybe 'device'. However, since it's specifically about keyboard input and display server (Wayland vs Xorg), I think 'graphic' is more appropriate because it involves how the graphical environment handles input events. +</think> + +The bug report is about incorrect handling of keyboard input in a Wayland session within QEMU. Since this pertains to the graphical interface's ability to capture and process key events, the most fitting category is: + +**graphic** \ No newline at end of file |