Fair questions, thanks for looking into this.

Q1 (reliably or typically?): "Typically" was deliberately cautious wording,
because after identifying the workaround we stopped systematically testing.
What we can say precisely: the crash occurred at session startup in EVERY
instance we observed during Nov 4-5, on two independent machines:

  * Machine 1 (laptop, Wayland): systemd-coredump Nov 5, 07:58 CET, SIGSEGV,
    identical stack trace
  * Machine 2 (desktop, Wayland): apport records from Nov 4 13:59 CET and a
    consecutive series of five SIGSEGVs on Nov 5 (09:31:01, 09:31:34,
    09:31:37, 09:31:40, 09:33:55 CET) while the session failed to come up
    (login loop appearance)

However, we also found a deterministic trigger that reproduces the crash
outside the reboot scenario: toggling the location setting

  gsettings set org.gnome.system.location enabled false/true

crashed the running shell IMMEDIATELY on both machines (user was logged out
to the GDM screen). This points squarely at the geolocation/weather fetch
path (libgweather) rather than anything boot-specific.

Q2 (extensions disabled -> no crash?): No, the crash still occurs with
extensions disabled. The five consecutive Nov 5 crashes quoted above happened
while org.gnome.shell disable-user-extensions was TRUE, i.e. all user
extensions globally off. The backtrace also contains no extension code
whatsoever: the crash path is libgweather-4.so.0 -> libsoup-3.0/libgio ->
xmlParseMemory -> __xmlRaiseError, with the SIGSEGV dispatched into
libxkbregistry.so.0 code (presumably via the process-global libxml2 error
handler).

The "extensions disappeared after update" impression in my original report
was purely a downstream symptom of GNOME's crash protection reacting to the
segfault (marker file + kill-switch), not a mitigation and not evidence that
extensions were involved.

Since masking geoclue (sudo systemctl mask geoclue.service), both machines
have been stable across multiple reboots, including first logins.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2173073

Title:
  gnome-shell 46.0-0ubuntu6~24.04.17 SIGSEGV in
  libgweather/xmlParseMemory during session start (first login after
  reboot)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2173073/+subscriptions


-- 
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to