-
Notifications
You must be signed in to change notification settings - Fork 613
xkbcommon FAQ
This page will list frequent questions and errors related to xkbcommon
In this case, you’re most likely on Debian or Ubuntu. You have several options to fix that:
- Use backports if the version is new enough.
- Build libxkbcommon by hand (not that complicated) but with a few configure switches:
./configure --with-x-locale-root=/usr/share/X11/locale --with-xkb-config-root=/usr/share/X11/xkb(or whatever correct prefix your system uses). This will make sure libxkbcommon knows where to look for files. - Use the repository maintained for the i3 window manager, which contains a recent libxkbcommon.
If you see that in rofi’s output, here are the possible reasons and their solution:
If you built libxkbcommon yourself, you will have to rebuild it but with ./configure --with-x-locale-root=/usr/share/X11/locale --with-xkb-config-root=/usr/share/X11/xkb (or whatever correct prefix your system uses).
If you used a custom repository, please contact the owner so they fixes their package.
Just check for the best locale in /usr/share/X11/locale/compose.dir, then use it.
Just check for variants of your locale in /usr/share/X11/locale/compose.dir and /usr/share/X11/locale/locale.alias, then use it.
Example: en_US.utf8 might not exist, try en_US.UTF-8.
Some keymaps are using features that used to exist in X11 XKB, but were removed in xkbcommon. You can find a complete list here.
These features are often not necessary and mostly used in customized or variants keymaps.
Related issues: #354