blob: 16023cc1ca555ae71e1788bb6fc8157a90b99d64 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
<think>
Okay, I need to classify this bug report into one of the given categories. Let's read through it carefully.
The issue is about the GTK+ interface not translating keycodes properly when using the Wayland backend in QEMU. The user provided some code snippets and explained how the current function gd_map_keycode doesn't handle certain keycodes correctly under Wayland, leading to invalid keycodes being sent.
Looking at the categories:
- Mistranslation relates to incorrect semantic mapping between source and target architectures. Here, the problem is with keycodes not being translated properly from GTK+ to QEMU's internal representation, which sounds like a mistranslation issue.
Other categories like 'device', 'graphic', etc., don't seem to fit as well because this isn't about hardware devices or graphical rendering but rather input handling.
So, the main problem is with how keycodes are being mapped incorrectly when using Wayland, which falls under the 'mistranslation' category.
</think>
The bug report discusses an issue where GTK+ keycodes aren't properly translated to QEMU's internal keycodes when running on a Wayland backend. This involves incorrect mapping between different keycode systems, fitting the 'mistranslation' category.
**Answer:**
mistranslation
|