Cannot change keyboard layout while on wayland session.

[Cristiandis]

Distribution

Linux Mint 22

Package version

6.2.0

Graphics hardware in use

Intel Corporation GeminiLake [UHD Graphics 600]

Frequency

Always

Bug description

Missing keyboard layout option while on wayland session.

Steps to reproduce

Open settings and go to keyboard.

Expected behavior

There should be a third button that open a menu where you can change the keyboard layout but its missing in wayland session.

Additional information

No response

[Leniwcowaty]

Can confirm, Linux Mint 21.3, no Keyboard Layout in Wayland and defaults to English, issue not present on X11

[stvoidit]

I will subscribe to this question.
So far, this problem is the only one for which I cannot fully use the Wayland session and test whenever possible.

[1vanK]

So far, this problem is the only one for which I cannot fully use the Wayland session and test whenever possible.

I also think this should be a higher priority.

[RossBrunton]

Dvorak user (btw) here. This is a blocker for me as well. I want to use Wayland (my GPU I think doesn't play nicely with X), but can't because of this.

[WhenGryphonsFly]

I regularly use the compose key (bound to scroll lock). I also have a custom XKB layout that classifies minus/underscore as alphabetic so that it is affected by caps lock. My understanding is that Wayland uses (or at least can use) XKB for keyboard layouts. Therefore, it is very annoying that even when an XKB layout (or compose key position) is manually set via dconf, the layout is not respected.

While I could struggle through the lack of underscore in caps lock, the lack of a compose key is a blocker for me. I believe I could also deal with the lack of ctrl+click (see issue 1), making this the sole blocker for me switching to Wayland for full-time testing.

I see that in #16 (before it was closed as a duplicate) that there is no timeline for work on this issue. I would be willing to work on this issue myself, but unfortunately I have too many other obligations to devote time to learning Cinnamon's codebase. Therefore, all I can ask is that the priority of this issue be reevaluated.

[ultraph]

will wait 4 this issue resolution.