> Crashing in getenv with a valid parameter like this should not be
possible so I think some heap corruption must have occurred before the
crash.

So at least as a hint coming from a report that was marked as a
duplicate of this - at least for me it's specifically when the system
had a monitor connected and it was disconnected that this issue occurs.

-- 
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/1979118

Title:
  gnome-shell crashed with SIGSEGV in __GI_getenv("NTCONFIG_SYSROOT")
  from IA__FcConfigGetSysRoot()

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


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

Reply via email to