SUMMARY: Keyboard with Finnish specification has an English American keyboard layout. Tested on Plasma on Wayland. Not aware of mean to determine the version of kxkb. EXPECTED RESULT: Correct layout by default. SOFTWARE/OS VERSIONS Operating System: Fedora 33 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION: Plasma on Wayland has the correct layout by default. Default in Plasma on Wayland: $ localectl System Locale: LANG=fi_FI.UTF-8 VC Keymap: fi X11 Layout: fi $ cat /etc/X11/xorg.conf.d/00-keyboard.conf | sed 1,3d Section "InputClass" Identifier "system-keyboard" MatchIsKeyboard "on" Option "XkbLayout" "fi" EndSection $ setxkbmap -query | column rules: evdev model: pc105 layout: us
Correction | Correct one has Gnome.
setxkbmap is a X11 tool and as such will not give you a meaningful result. On recent versions there is indeed a warning: `WARNING: Running setxkbmap against an Xwayland server`. Is you issue incorrect layout for X11 apps or merely incorrect result with `setxkbmap -query`?
I lastly figured out on Fedora 40 Desktop edition, a systemd Linux distribution, a way to change the Keymap in the current session, though while being on Gnome v. 46 . on Wayland (Mutter as compositor), and on a tty, not a pts device. ``` $ tty /dev/tty3 $ kbd_mode The keyboard is in Unicode (UTF-8) mode $ inxi -G | grep '^ Display' Display: server: X.org v: 1.20.14 with: Xwayland v: 23.2.6 driver: gpu: i915 note: X driver $ sudo loadkeys -C /dev/tty3 fi ``` Not printing 'localectl' as it wouldn't be meaningful, showing 'VC Keymap' still as 'us' not as 'fi'; it shows the current configuration, not what has been loaded into the kernel. kbd-utilities work at a lower level. 'systemd' uses kbd-utilities to configure the console. I assume all those observations are viable in the version of KDE Plasma Desktop that is produced as a variant of Fedora Desktop. Shall be closed accordingly.
After a lot of googling and some debugging I found this issue: Some X11 applications, like xfreerdp or some not yet wayland compatible applications that do similar things (anydesk as client to some extend) query X for the keyboard layout and use "scancodes". This results in the case of xfreerdp to always use the wrong keyboard layout. Applications that only take the "usual" input of course work, only applications that work with scancodes seem to be affected. setxkbmap works around this issue, although I'm not sure if this has some negative effects. If there should not be any regressions I would say it makes sense for plasma to sync that attribute (if at the end it is effectively only an attribute in Xwayland's case, but again, I did not check that)