Bug 1225612 - Unable to switch keyboard layout in XWayland applications.
Summary: Unable to switch keyboard layout in XWayland applications.
Status: RESOLVED DUPLICATE of bug 1219505
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: X.Org (show other bugs)
Version: Leap 15.6
Hardware: x86-64 Other
: P3 - Medium : Major (vote)
Target Milestone: ---
Assignee: Gfx Bugs
QA Contact: Gfx Bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-29 13:52 UTC by Oleg Kalugin
Modified: 2024-05-30 09:54 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
sndirsch: needinfo? (i)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Oleg Kalugin 2024-05-29 13:52:52 UTC
On openSUSE 15.6 (Both GNOME and KDE) it's impossible to switch keyboard layout in XWayland applications, while switching works perfectly fine with Wayland-native applications or in X11 session for all apps. 

I experienced this bug in VSCode, IntelliJ IDEA, WebStorm, DataGrip, Minecraft.
Comment 1 Stefan Dirsch 2024-05-29 14:35:39 UTC
How are you trying to change the keyboard in Xwayland? Please give me an example.
Comment 2 Oleg Kalugin 2024-05-29 16:58:52 UTC
Just as usual, using Alt+Shift or Caps Lock.
Comment 3 Stefan Dirsch 2024-05-29 20:50:09 UTC
I'm not sure if using hotkeys can work in Xwayland without any desktop running in inside this Xserver. I would try using

  setxkbmap 

instead for testing.
Comment 4 Oleg Kalugin 2024-05-30 08:13:51 UTC
Hotkeys in XWayland work in Leap 15.5
Comment 5 Lubos Kocman 2024-05-30 08:47:03 UTC
Most likely a duplicate of Bug 1219505
Comment 6 Alynx Zhou 2024-05-30 08:52:04 UTC
Let me have a look at this.
Comment 7 Oleg Kalugin 2024-05-30 08:57:36 UTC
(In reply to Lubos Kocman from comment #5)
> Most likely a duplicate of Bug 1219505

Yes
Comment 8 Stefan Dirsch 2024-05-30 09:54:40 UTC
Ok. So let's close it as such.

*** This bug has been marked as a duplicate of bug 1219505 ***