Package: libxkbregistry0 Version: 1.7.0-2 Severity: important Tags: upstream fixed-upstream
On Debian 13 amd64, GNOME Shell 48.7 repeatedly segfaulted, returning me to the login screen. This affected both normal GNOME and GNOME Classic, including while idle, and occurred with third-party extensions disabled. A core dump with matching debug symbols showed: invalid callback address rxkb_log src/registry.c:149 xml_error_func src/registry.c:1151 xmlReportError / __xmlRaiseError xmlParseMemory parse_forecast_xml_new libgweather/weather-metno.c:304 metno_finish_new libgweather/weather-metno.c:423 The XML error was: "Premature end of data in tag location line 133" This matches the known dangling libxml2 error-handler bug: https://github.com/xkbcommon/libxkbcommon/issues/529 Upstream fix: https://github.com/xkbcommon/libxkbcommon/pull/530 Before upgrading, a standalone test confirmed the XML error handler still referenced the freed registry context. Upgrading the libxkbcommon family to 1.13.1-1~bpo13+1 from trixie-backports cleared the dangling handler. Parsing malformed XML afterward no longer crashes the test process. Could the upstream fix also be included in Debian 13 stable?
