/usr/share/apport/apport-gtk:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard

[errors.ubuntu.com bug bridge]

The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.27.0-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/196d97dec8fe94e52eebaf9e7da150d1629a1e05 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

g_log_structured_standard (log_domain=log_domain@entry=0x7f7fa9a12014 "Gtk", log_level=log_level@entry=G_LOG_LEVEL_ERROR, file=file@entry=0x7f7fa9a4e7c0 "../../../gtk/gtkstylecontext.c", line=line@entry=0x7f7fa9a1a381 "348", func=func@entry=0x7f7fa9a849a0 <__func__.70> "gtk_style_context_init", message_format=message_format@entry=0x7f7fa9a4edf0 "Can't create a GtkStyleContext without a display connection")

This crash is probably a different variant of bug #1842439 but I cannot reproduce this crash (by running "killall -11 gnome-shell" on a mantic system).

This bug is the top 1 apport bug in Ubuntu 23.10 (mantic).

[Benjamin Drung (bdrung)]

This needs to be fixed in gtk+3.0 to not crash but raise an exception instead (that can be caught by apport).

[Julian Andres Klode (juliank)]

Is desktop aware this is for desktop to solve on gtk+3.0 side first?

[Sebastien Bacher (seb128)]

Desktop is aware but it's not likely we will have the resources to work on that issue this cycle