Hi Antonio, > We probably want to fix the code to *not* segfault when the workaround > is not in place.
Agreed! > I'm not sure whether this is a bug in gtg itself, or > in pango. The issue is likely in the g_object_get_property or in pango_font_description_to_string, or in the code calling both methods in GTG/gtk/general_preferences.py For now, I've followed the upstream advice to revert the behavior to get a default font when font_name is not available, hence by-passing the two problematic methods. I've just committed the patch [1], and I'll likely upload a new package shortly to prevent package removal. Let me know if this sounds acceptable to you. Best, François [1] https://salsa.debian.org/python-team/packages/gtg/-/commit/e9ac644f40629704a4e85b56ff887a59d6748d58
signature.asc
Description: This is a digitally signed message part
