gnome-control-center crashed with SIGSEGV in gtk_widget_in_destruction() from gcm_prefs_list_box_row_selected_cb() from g_cclosure_marshal_VOID__OBJECTv() from _g_closure_invoke_va() from g_signal_emit_valist()

[errors.ubuntu.com bug bridge]

The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:44~alpha-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/bc1ff846df442e10c2163a5598d9e284da404c11 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/.

[Daniel van Vugt (vanvugt)]

This is the #1 crasher for gnome-control-center in lunar.

[Marco Trevisan (Treviño) (3v1n0)]

Valgrind confirms:

==22708== Invalid read of size 1
==22708== at 0x505CC0B: gtk_widget_in_destruction (gtkwidget.c:10643)
==22708== by 0x189553: gcm_prefs_list_box_row_selected_cb (cc-color-panel.c:1708)
==22708== by 0x4A61714: g_cclosure_marshal_VOID__OBJECTv (gmarshal.c:1910)
==22708== by 0x4A5E148: _g_closure_invoke_va (gclosure.c:895)
==22708== by 0x4A784F3: g_signal_emit_valist (gsignal.c:3462)
==22708== by 0x4A78722: g_signal_emit (gsignal.c:3612)
==22708== by 0x4F5B121: gtk_list_box_remove (gtklistbox.c:2420)
==22708== by 0x4F5B222: gtk_list_box_dispose (gtklistbox.c:439)
==22708== by 0x4A63338: g_object_unref (gobject.c:3891)
==22708== by 0x4EAA994: gtk_box_dispose (gtkbox.c:230)
==22708== by 0x4A63338: g_object_unref (gobject.c:3891)
==22708== by 0x4EAA994: gtk_box_dispose (gtkbox.c:230)
==22708== Address 0xfffffffffffffeb2 is not stack'd, malloc'd or (recently) free'd
==22708==
==22708==
==22708== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==22708== Access not within mapped region at address 0xFFFFFFFFFFFFFEB2
==22708== at 0x505CC0B: gtk_widget_in_destruction (gtkwidget.c:10643)
==22708== by 0x189553: gcm_prefs_list_box_row_selected_cb (cc-color-panel.c:1708)
==22708== by 0x4A61714: g_cclosure_marshal_VOID__OBJECTv (gmarshal.c:1910)
==22708== by 0x4A5E148: _g_closure_invoke_va (gclosure.c:895)
==22708== by 0x4A784F3: g_signal_emit_valist (gsignal.c:3462)
==22708== by 0x4A78722: g_signal_emit (gsignal.c:3612)
==22708== by 0x4F5B121: gtk_list_box_remove (gtklistbox.c:2420)
==22708== by 0x4F5B222: gtk_list_box_dispose (gtklistbox.c:439)
==22708== by 0x4A63338: g_object_unref (gobject.c:3891)
==22708== by 0x4EAA994: gtk_box_dispose (gtkbox.c:230)
==22708== by 0x4A63338: g_object_unref (gobject.c:3891)
==22708== by 0x4EAA994: gtk_box_dispose (gtkbox.c:230)
==22708== If you believe this happened as a result of a stack
==22708== overflow in your program's main thread (unlikely but
==22708== possible), you can try to increase the size of the
==22708== main thread stack using the --main-stacksize= flag.
==22708== The main thread stack size used in this run was 8388608.

[Marco Trevisan (Treviño) (3v1n0)]

Fixed in https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/4b400736bc7374d0c74b498c1f60dedaa5fe9c4b

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-control-center - 1:44.0-1ubuntu3

---------------
gnome-control-center (1:44.0-1ubuntu3) lunar; urgency=medium

  * debian/patches: Recolor widget animations instead of using many.
    Reduce gresources by just providing default yaru color for animations
    and while keeping the same colors recoloring them at runtime.
  * debian/patch: Prevent duplicate sound device entries
  * debian/patches: Do not crash when closing the color panel (LP: #2009913)

 -- Marco Trevisan (Treviño) <email address hidden> Thu, 23 Mar 2023 06:36:00 +0100