| Summary: | Keyboard layout is not correctly set for XWayland clients. Probably related to #444012 | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Victor Sanchez <vsanchez> |
| Component: | kcm_keyboard | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | butirsky, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.23.1 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Victor Sanchez
2021-10-20 15:58:32 UTC
Does it work if you reopen XWayland window after reconfiguring layouts? Hmm, changing in kcm_layout the layout to "us" (from "latam") changes the layout also for XWayland (in this case an electron app). However setkbmap keeps printing that the keyboard map is "latam".... (!) Same issue as Bug 444012? It seems to me. I asked and he was also running in wayland and the problem is not there in X11. He used google chrome as an example of the program with problems. By default that program runs (in kubuntu 21.10) in XWayland. You can force it to run in wayland using the Ozoneplatform and then it uses the correct keymap. (BTW this does not work with electron based apps that use chromium, trying to use the Ozone platform gives an error). The same can be said of thunderbird. Running it in Xwayland vs forcing it to run under wayland (using MOZ_ENABLE_WAYLAND=1). *** This bug has been marked as a duplicate of bug 444012 *** |