Fix .deb bundle: restore XKB and fontconfig paths in wrapper

The XKB_CONFIG_ROOT, FONTCONFIG_FILE, and FONTCONFIG_PATH exports were
accidentally removed in e68a5fef (SSL certificate fix). Without these,
the bundled libxkbcommon falls back to a hardcoded CI runner path that
does not exist on the target system, causing xkb_context_new to return
NULL and SIGSEGV in xkb_context_ref during Wayland keyboard init at
splash screen startup.
This commit is contained in:
forbes
2026-01-30 09:58:14 -06:00
parent 9dc50cef72
commit a9c444131a

View File

@@ -105,6 +105,13 @@ export PYTHONPATH="${KINDRED_CREATE_HOME}/lib/python3.11:${KINDRED_CREATE_HOME}/
export XDG_DATA_DIRS="${KINDRED_CREATE_HOME}/share:${XDG_DATA_DIRS:-/usr/share}"
export GI_TYPELIB_PATH="${KINDRED_CREATE_HOME}/lib/girepository-1.0:${GI_TYPELIB_PATH:-}"
# XKB keyboard configuration - use bundled data to avoid hardcoded CI paths in libxkbcommon
export XKB_CONFIG_ROOT="${KINDRED_CREATE_HOME}/share/X11/xkb"
# Fontconfig - use bundled configuration to avoid missing default config
export FONTCONFIG_FILE="${KINDRED_CREATE_HOME}/etc/fonts/fonts.conf"
export FONTCONFIG_PATH="${KINDRED_CREATE_HOME}/etc/fonts"
# Use system CA certificates so bundled Python trusts internal CAs (e.g. FreeIPA)
# The bundled openssl has a hardcoded cafile from the build environment which
# does not exist on the target system.