[Bug 58247] New: ABNT Keyboard Not Working Properly in Wine with Wayland Driver
http://bugs.winehq.org/show_bug.cgi?id=58247 Bug ID: 58247 Summary: ABNT Keyboard Not Working Properly in Wine with Wayland Driver Product: Wine Version: 10.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: xnep1(a)hotmail.com Distribution: --- Created attachment 78588 --> http://bugs.winehq.org/attachment.cgi?id=78588 Tracefile with winedebug=keyboard,key showing "/" not working When running Wine applications using the Wayland driver, certain keys on the Brazilian ABNT2 keyboard (such as the slash /, question mark ?, and other special characters) do not function correctly. These keys either generate no character. In contrast, when using the X11 driver (wine X11), the same keys function as expected, and the correct characters are produced. Upon inspection, the scan codes received under Wayland are extended (e.g., 0x259 instead of 0x59 for the slash key), which seems to lead to incorrect mapping or interpretation by Wine. This issue appears to stem from incomplete or incorrect handling of extended scan codes or keyboard layout mapping for the br-abnt2 layout in the Wayland input. In my tests, I forced the correct scan code for the slash key (0x59), and after this adjustment, the key started working properly again. I have attached a trace log file showing the key input events during the failure. Although I am currently using a modified version of Wine to generate this trace, the problem also occurs on the stable Wine release. (It's late and I'm not going to redo the test just to have a clean trace file. Sorry.) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=58247 mata <sutupud(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sutupud(a)yahoo.com --- Comment #1 from mata <sutupud(a)yahoo.com> --- This reads like it's related to https://bugs.winehq.org/show_bug.cgi?id=57097 The "workaround" there is to set LC_ALL according to your locale - but of course that is not really a portable solution. But you might want to check if that does anything for you. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=58247 --- Comment #2 from xnep1(a)hotmail.com --- (In reply to mata from comment #1)
This reads like it's related to https://bugs.winehq.org/show_bug.cgi?id=57097
The "workaround" there is to set LC_ALL according to your locale - but of course that is not really a portable solution. But you might want to check if that does anything for you.
Indeed, they look similar. I set my LC_ALL=pt_BR.utf8 And the problem persists. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=58247 daniel <daniel.penalized(a)proton.me> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.penalized(a)proton.me --- Comment #3 from daniel <daniel.penalized(a)proton.me> --- Created attachment 78599 --> http://bugs.winehq.org/attachment.cgi?id=78599 output log This problem also happens to me. It's not just / and ? that don't work, the accents (ä, á, à, ã, â) don't work either! LC_ALL=pt_BR.UTF-8 doesn't solve this problem. In this log, I ran notepad with LC_ALL=pt_BR.UTF-8 WAYLAND_DEBUG=1 WINEDEBUG=+key,+keyboard,+pid,+system,+tid,+timestamp,+waylanddrv,+win and tried typing all the characters that winewayland.drv doesn't support: ä, á, à, ã, â, / and ?. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=58247 Totto <tobiausgais(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tobiausgais(a)gmail.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=58247 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |hardware, localization, | |source -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=58247 n5u6jpck8@mozmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |n5u6jpck8@mozmail.com --- Comment #4 from n5u6jpck8@mozmail.com --- if it was a layout problem i think ç should have not worked and it seems the arrows are not working in some game too when using wayland -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=58247 --- Comment #5 from xnep1@hotmail.com --- (In reply to someoneenoyingbybugs from comment #4)
if it was a layout problem i think ç should have not worked and it seems the arrows are not working in some game too when using wayland
It’s not exactly an issue with the layouts themselves. However, the Wayland keyboard code doesn't handle scancodes from non-US layouts very well. "Ç" works because, in the ABNT2 layout, its physical key corresponds to `KEY_SEMICOLON`, which exists in the US layout. The "/?" key, on the other hand, comes from the ISO standard and uses `KEY_RO`. The arrow keys should be working; they work fine for me. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (2)
-
WineHQ Bugzilla -
WineHQ Bugzilla