https://bugs.kde.org/show_bug.cgi?id=491982
--- Comment #17 from Gauthier <[email protected]> --- (In reply to Wismill from comment #16) > Are your problematic applications running with native Wayland support or X11? > > I set *3* layouts us,fr,de > > I tried using Chromium (*not* flatpack) in both case and I observe the > following: > - chromium --ozone-platform=wayland: no issue > - chromium --ozone-platform=x11: pressing Caps, > - Having first layout US active: Q gives Q (expected A), Y gives Z > (expected Y); > - Having second layout FR active: Q gives Q (ok) but Y gives Y (expected Z) > > So it seems that the group modifier is applied twice. In the case without > only two layouts, it actually wraps to the first layout, so you observe no > effect. > > But wait, I can observe this behavior in Gtk apps using e.g. > `GDK_BACKEND=x11 gnome-text-editor` and Qt app e.g. QT_QPA_PLATFORM=xcb > kate`. > > This seems to be an X11 bug only. Keep in mind this is for a Wayland session > only, I have not tried a proper X11 session. I can reproduce this behaviour. I tried Chromium with --ozone-platform=wayland and it works fine. The app I tried were ungoogle chromium, chromium, Signal Desktop, Jitis, Freetube and they are indeed not running native wayland. The issue is now solved for all of them as I have flags so they start with wayland. Thank you!! I guess while this is a bug for X11 apps running under wayland, but whether or not it is worth fixing I'm not sure (niche case + workarounds available). -- You are receiving this mail because: You are watching all bug changes.
