I could reproduce the crash in a docker container.
The libxkbcommon fix works:
- 1.6.0 and 1.7.0 crashed
- 1.8.0 is fixed and did produce a clean parse error.
- 1.6.0 + only the upstream fix produced a clean parse error.
---
Data point against the libsoup theory, from an affected 24.04 machine:
- libsoup-3.0 3.4.4-5ubuntu0.10 was installed here on 2026-11-04 09:01 CET.
- In the weeks before that, gnome-shell logged no "TLS handshake failed" at
all; weather fetches (METAR and met.no) worked normally.
- A Home Assistant instance on another host (Python/aiohttp, no libsoup)
started logging met.no failures on 2026-11-04 08:52 CET, before the libsoup
update: repeated HTTP 503, plus HTML error bodies ("Unable to parse json") at
2026-11-04 08:52 and 2026-11-05 08:33.
- The gnome-shell crashes here line up with met.no returning an HTML error page
(e.g. "Failed to get met.no forecast data: [status: 502] Bad Gateway" one line
before "GNOME Shell crashed with signal 11").
- The 0ubuntu0.10 changelog only touches data-URI decoding and WebSockets, not
TLS.
So the trigger appears to be met.no serving error pages since 2026-11-04
~08:52 CET; the libsoup update landing the same day looks coincidental.
The underlying bug remains the dangling libxml2 error handler in
libxkbregistry (upstream libxkbcommon issue 529, fixed in 1.8.0).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2172923
Title:
xkbregistry leaves dangling libxml2 error handler → gnome-shell
SIGSEGV when libgweather parses malformed XML
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/2172923/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
