diff options
Diffstat (limited to 'results/classifier/deepseek-2-tmp/reasoning/graphic/1642011')
| -rw-r--r-- | results/classifier/deepseek-2-tmp/reasoning/graphic/1642011 | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/results/classifier/deepseek-2-tmp/reasoning/graphic/1642011 b/results/classifier/deepseek-2-tmp/reasoning/graphic/1642011 new file mode 100644 index 000000000..ae1dfb77f --- /dev/null +++ b/results/classifier/deepseek-2-tmp/reasoning/graphic/1642011 @@ -0,0 +1,15 @@ +<think> +Okay, so I'm trying to classify this bug report about QEMU. The issue is that mouse wheel events aren't being forwarded to the guest when using GTK display. Let me break it down. + +First, the user is running QEMU 2.7.0 with KVM enabled. They're using the default display option, which is GTK. When they scroll the mouse wheel, nothing happens in the guest. However, if they use the 'sdk' display option, it works fine. + +The command line they provided includes various settings like -vga cirrus, -usbdevice mouse, and network configurations. They also mention that checking /dev/input doesn't show any events when scrolling, indicating the issue is with event forwarding. + +Looking at the possible categories: mistranslation, assembly, other, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor. + +This seems related to how input events are handled. Mouse wheel events not being sent suggests a problem with the display or input handling in QEMU's GTK frontend. The 'display' part of QEMU is under the graphics category, so graphic makes sense here. Alternatively, it could be a device issue since it's about USB devices (mouse), but the main problem seems to be with how events are handled by the display. + +I think 'graphic' is the most appropriate category because it directly relates to the display handling and input events in the graphical interface. +</think> + +graphic \ No newline at end of file |