https://bugs.kde.org/show_bug.cgi?id=447206
Bug ID: 447206
Summary: kwin_wayland ignores $XDG_CONFIG_HOME/xkb
Product: kwin
Version: 5.23.4
Platform: Debian unstable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: platform-wayland
Assignee: kwin-bugs-n...@kde.org
Reporter: marc+b...@mezzarobba.net
Target Milestone: ---
SUMMARY
kwin_wayland supports getting its xkb configuration from the environment
variables XKB_DEFAULT_LAYOUT, and libxkbcommon's default include paths include
$XDG_CONFIG_HOME/xkb. This should make it possible to load a custom keymap from
~/.config/xkb when launching kwin as a wayland compositor, even though
kcm_keyboard only supports keymaps from the system-wide xkb library.
However, on my system, kwin only looks in /usr/share/X11/xkb/ and /etc/xkb when
loading the keymap, not in the other standard locations $HOME/.xkb and
$XDG_CONFIG_HOME/xkb.
STEPS TO REPRODUCE
1. put a custom keymap "mylayout" in $HOME/.config/xkb
2. create .config/plasma-workspace/env/setkeymap.sh containing
export QT_LOGGING_RULES="kwin_*.debug=true"
export XKB_LOG_VERBOSITY=10
export KWIN_XKB_DEFAULT_KEYMAP=yes
export XKB_DEFAULT_LAYOUT=mylayout
3. launch plasma session
OBSERVED RESULT
The custom keymap is not used. The logs in
.local/share/sddm/wayland-session.log confirm that libxkbcommon only searched
/usr/share/X11/xkb/ and /etc/xkb.
ADDITIONAL INFORMATION
Possibly related to #388249?
On a single-user machine, a possible workaround is to put one's custom keymaps
in /etc/xkb.
--
You are receiving this mail because:
You are watching all bug changes.
