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.

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

Title:
  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()

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  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/.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to