[Bug 53991] New: libx11 1.8.2 break bepo keyboard layout

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=53991

Bug ID: 53991
           Summary: libx11 1.8.2 break bepo keyboard layout
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: winex11.drv
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Hello,

Since upgrading my ArchLinux system, the upgrade of libx11 from 1.8.1 to 1.8.2
breaks my bepo layout and some key are not detected in a weird way.

Restarting Guild Wars 2 game after libx11 upgrade just change "randomly" some
assigned key, from `É` to `=` and from `È` to `É`. Trying to reassign keys
doesn't work, `É` can be assign to previous skill, but `È` key just doesn't
work at all, it's no more detected as a valid input in skill selection windows.
But this `È` key works perfectly if used on an input text field like the ingame
chat.

Downgrading to 1.8.1 and restarting the game fix the trouble.

Behaviour seen at least in lutris-7.2.2 and lutris-ge-proton 7.34.

Don't know if this is related or not, but currently bepo layout is badly
managed by wine and i try to add support for it in
https://bugs.winehq.org/show_bug.cgi?id=48650 but never really succeed to
create something really good.

[Bug 53991] libx11 1.8.2 break bepo keyboard layout

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=53991

--- Comment #1 from aeris  ---
Created attachment 73575
  --> https://bugs.winehq.org/attachment.cgi?id=73575
key assign in 1.8.1

[Bug 53991] libx11 1.8.2 break bepo keyboard layout

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=53991

--- Comment #2 from aeris  ---
Created attachment 73576
  --> https://bugs.winehq.org/attachment.cgi?id=73576
key assign after 1.8.2 upgrade and restarting the game

[Bug 53991] libx11 1.8.2 break bepo keyboard layout

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=53991

--- Comment #3 from aeris  ---
Seems this bug is related to a fix in libx11.
https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/179#note_1806555

I don't know how to reply to this x11 developer.
Does Wine implement "weird" way to handle previously wrong keyboard behavior
and then this fix in libx11 cause a regression?

Regards,

[Bug 53991] libx11 1.8.2 break bepo keyboard layout

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=53991

Rémi Bernon  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #4 from Rémi Bernon  ---
Fwiw Wine is known to incorrectly detect many keyboard layouts. See
https://bugs.winehq.org/show_bug.cgi?id=30984 and
https://bugs.winehq.org/show_bug.cgi?id=45605. I'm working on making things
better.

Would you mind attaching a log file with WINEDEBUG=+key,+keyboard environment
variable set, before and after the problematic Xlib version?

Please use pristine Wine, without any additional patches. There's been some
patches trying to address these keyboard layout problems floating around, but I
don't think they fixed them entirely.

I've also recently submitted an update to the related Wine Staging patch series
(https://gitlab.winehq.org/wine/wine-staging/-/tree/master/patches/winex11-Fi...),
which might help your case as well.

[Bug 53991] libx11 1.8.2 break bepo keyboard layout

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=53991

Timo Zuccarello  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]