• gnome-control-c crashing


    Hello,
    the settings on gnome won’t open - directly or through var. sub-menus (like network settings or account settings BT settings etc. ).
    Logs show

    Process 1919 (gnome-control-c) crashed and dumped core.
    
    Process 1919 (gnome-control-c) of user 1000 dumped core.
    
    Stack trace of thread 1919:
    #0  0x00007fee28818f41 __libc_free (libc.so.6)
    #1  0x00007fee2867bd7a g_unix_mount_free (libgio-2.0.so.0)
    #2  0x0000560d91670f04 n/a (gnome-control-center)
    #3  0x0000560d9167679b n/a (gnome-control-center)
    #4  0x00007fee28593722 g_type_create_instance (libgobject-2.0.so.0)
    #5  0x00007fee285b1509 n/a (libgobject-2.0.so.0)
    #6  0x00007fee285b2154 g_object_new_valist (libgobject-2.0.so.0)
    #7  0x00007fee285b2aea g_object_new (libgobject-2.0.so.0)
    #8  0x0000560d916a64b9 n/a (gnome-control-center)
    #9  0x00007fee285ab067 g_cclosure_marshal_VOID__STRINGv (libgobject-2.0.so.0)
    #10 0x00007fee2859d3b5 g_signal_emit_valist (libgobject-2.0.so.0)
    #11 0x00007fee2859e080 g_signal_emit (libgobject-2.0.so.0)
    #12 0x0000560d916a4502 n/a (gnome-control-center)
    #13 0x00007fee285abe75 g_closure_invoke (libgobject-2.0.so.0)
    #14 0x00007fee28598fd5 n/a (libgobject-2.0.so.0)
    #15 0x00007fee2859d1ae g_signal_emit_valist (libgobject-2.0.so.0)
    #16 0x00007fee2859e080 g_signal_emit (libgobject-2.0.so.0)
    #17 0x00007fee2859d3b5 g_signal_emit_valist (libgobject-2.0.so.0)
    #18 0x00007fee2859dd62 g_signal_emit_by_name (libgobject-2.0.so.0)
    #19 0x0000560d916a3e9a cc_panel_list_set_active_panel (gnome-control-center)
    #20 0x0000560d916a8f30 n/a (gnome-control-center)
    #21 0x00007fee285b1753 n/a (libgobject-2.0.so.0)
    #22 0x00007fee285b2154 g_object_new_valist (libgobject-2.0.so.0)
    #23 0x00007fee285b2aea g_object_new (libgobject-2.0.so.0)
    #24 0x0000560d916a52a0 cc_window_new (gnome-control-center)
    #25 0x0000560d916a916c n/a (gnome-control-center)
    #26 0x00007fee285abe75 g_closure_invoke (libgobject-2.0.so.0)
    #27 0x00007fee28599188 n/a (libgobject-2.0.so.0)
    #28 0x00007fee2859d1ae g_signal_emit_valist (libgobject-2.0.so.0)
    #29 0x00007fee2859e080 g_signal_emit (libgobject-2.0.so.0)
    #30 0x00007fee286760b4 g_application_register (libgio-2.0.so.0)
    #31 0x00007fee286771cc n/a (libgio-2.0.so.0)
    #32 0x00007fee28676ebb g_application_run (libgio-2.0.so.0)
    #33 0x0000560d915a0359 main (gnome-control-center)
    #34 0x00007fee287b7223 __libc_start_main (libc.so.6)
    #35 0x0000560d915a03ae _start (gnome-control-center)
    
    Stack trace of thread 1924:
    #0  0x00007fee28964afc [email protected]@GLIBC_2.3.2 (libpthread.so.0)
    #1  0x00007fee1653cab4 n/a (radeonsi_dri.so)
    #2  0x00007fee1653c7d8 n/a (radeonsi_dri.so)
    #3  0x00007fee2895ea9d start_thread (libpthread.so.0)
    #4  0x00007fee2888eb23 __clone (libc.so.6)
    
    Stack trace of thread 1925:
    #0  0x00007fee28964afc [email protected]@GLIBC_2.3.2 (libpthread.so.0)
    #1  0x00007fee1653cab4 n/a (radeonsi_dri.so)
    #2  0x00007fee1653c7d8 n/a (radeonsi_dri.so)
    #3  0x00007fee2895ea9d start_thread (libpthread.so.0)
    #4  0x00007fee2888eb23 __clone (libc.so.6)
    
    Stack trace of thread 1933:
    #0  0x00007fee28964afc [email protected]@GLIBC_2.3.2 (libpthread.so.0)
    #1  0x00007fee1653cab4 n/a (radeonsi_dri.so)
    #2  0x00007fee1653c7d8 n/a (radeonsi_dri.so)
    #3  0x00007fee2895ea9d start_thread (libpthread.so.0)
    #4  0x00007fee2888eb23 __clone (libc.so.6)
    
    Stack trace of thread 1921:
    #0  0x00007fee28883c21 __poll (libc.so.6)
    #1  0x00007fee284c0690 n/a (libglib-2.0.so.0)
    #2  0x00007fee284c077e g_main_context_iteration (libglib-2.0.so.0)
    #3  0x00007fee284c07d2 n/a (libglib-2.0.so.0)
    #4  0x00007fee2849bc21 n/a (libglib-2.0.so.0)
    #5  0x00007fee2895ea9d start_thread (libpthread.so.0)
    #6  0x00007fee2888eb23 __clone (libc.so.6)
    
    Stack trace of thread 1929:
    #0  0x00007fee28964afc [email protected]@GLIBC_2.3.2 (libpthread.so.0)
    #1  0x00007fee1653cab4 n/a (radeonsi_dri.so)
    #2  0x00007fee1653c7d8 n/a (radeonsi_dri.so)
    #3  0x00007fee2895ea9d start_thread (libpthread.so.0)
    #4  0x00007fee2888eb23 __clone (libc.so.6)
    
    Stack trace of thread 1923:
    #0  0x00007fee28964afc [email protected]@GLIBC_2.3.2 (libpthread.so.0)
    #1  0x00007fee1653cab4 n/a (radeonsi_dri.so)
    #2  0x00007fee1653c7d8 n/a (radeonsi_dri.so)
    #3  0x00007fee2895ea9d start_thread (libpthread.so.0)
    #4  0x00007fee2888eb23 __clone (libc.so.6)
    
    Stack trace of thread 1927:
    #0  0x00007fee28964afc [email protected]@GLIBC_2.3.2 (libpthread.so.0)
    #1  0x00007fee1653cab4 n/a (radeonsi_dri.so)
    #2  0x00007fee1653c7d8 n/a (radeonsi_dri.so)
    #3  0x00007fee2895ea9d start_thread (libpthread.so.0)
    #4  0x00007fee2888eb23 __clone (libc.so.6)
    
    Stack trace of thread 1926:
    #0  0x00007fee28964afc [email protected]@GLIBC_2.3.2 (libpthread.so.0)
    #1  0x00007fee1653cab4 n/a (radeonsi_dri.so)
    #2  0x00007fee1653c7d8 n/a (radeonsi_dri.so)
    #3  0x00007fee2895ea9d start_thread (libpthread.so.0)
    #4  0x00007fee2888eb23 __clone (libc.so.6)
    
    Stack trace of thread 1931:
    #0  0x00007fee28964afc [email protected]@GLIBC_2.3.2 (libpthread.so.0)
    #1  0x00007fee1653cab4 n/a (radeonsi_dri.so)
    #2  0x00007fee1653c7d8 n/a (radeonsi_dri.so)
    #3  0x00007fee2895ea9d start_thread (libpthread.so.0)
    #4  0x00007fee2888eb23 __clone (libc.so.6)
    
    Stack trace of thread 1928:
    #0  0x00007fee28964afc [email protected]@GLIBC_2.3.2 (libpthread.so.0)
    #1  0x00007fee1653cab4 n/a (radeonsi_dri.so)
    #2  0x00007fee1653c7d8 n/a (radeonsi_dri.so)
    #3  0x00007fee2895ea9d start_thread (libpthread.so.0)
    #4  0x00007fee2888eb23 __clone (libc.so.6)
    
    Stack trace of thread 1922:
    #0  0x00007fee28883c21 __poll (libc.so.6)
    #1  0x00007fee284c0690 n/a (libglib-2.0.so.0)
    #2  0x00007fee284c16d2 g_main_loop_run (libglib-2.0.so.0)
    #3  0x00007fee28632568 n/a (libgio-2.0.so.0)
    #4  0x00007fee2849bc21 n/a (libglib-2.0.so.0)
    #5  0x00007fee2895ea9d start_thread (libpthread.so.0)
    #6  0x00007fee2888eb23 __clone (libc.so.6)
    
    Stack trace of thread 1930:
    #0  0x00007fee28964afc [email protected]@GLIBC_2.3.2 (libpthread.so.0)
    #1  0x00007fee1653cab4 n/a (radeonsi_dri.so)
    #2  0x00007fee1653c7d8 n/a (radeonsi_dri.so)
    #3  0x00007fee2895ea9d start_thread (libpthread.so.0)
    #4  0x00007fee2888eb23 __clone (libc.so.6)
    
    Stack trace of thread 1934:
    #0  0x00007fee28883c21 __poll (libc.so.6)
    #1  0x00007fee284c0690 n/a (libglib-2.0.so.0)
    #2  0x00007fee284c077e g_main_context_iteration (libglib-2.0.so.0)
    #3  0x00007fee1428fbde n/a (libdconfsettings.so)
    #4  0x00007fee2849bc21 n/a (libglib-2.0.so.0)
    #5  0x00007fee2895ea9d start_thread (libpthread.so.0)
    #6  0x00007fee2888eb23 __clone (libc.so.6)
    

    also

    gnome-control-center -v
    
    (gnome-control-center:4499): Gtk-WARNING **: 17:11:55.738: Theme parsing error: gtk.css:2281:23: Expected a valid selector
    
    (gnome-control-center:4499): Gtk-WARNING **: 17:11:55.745: Theme parsing error: gtk.css:11535:3: '/*' in comment block
    
    (gnome-control-center:4499): Gtk-WARNING **: 17:11:55.745: Theme parsing error: gtk.css:11641:2: '/*' in comment block
    fish: “gnome-control-center -v” terminated by signal SIGSEGV (Address boundary error)
    
    

    I tried several “workarounds” for similar situations with no effect.
    reinstalling and starting avahi-daemon.service, removing and installing gnome-control-center.

    I’ve also reinstalled and ended up in the same situation. The control c breaks when accessing the user settings and after that it’s gone. Could be relevant or coincidence.

    Any help will be appreciated.

  • @reginastracii said in gnome-control-c crashing:

    gnome-control-center

    possible that the used gtk-theme is causing this…

     Gtk-WARNING **: 17:11:55.738: Theme parsing error: gtk.css
    
  • Reversing everything to default theming and disabling all gnome extensions has no effect.

  • I have finished installing now a new fresh system with cnchi 19.3 version and there is the same error…

  • I did a fresh reinstall to rule out any themes and tweaks as a cause. Same thing happens.

    edit: Also happens with Budgie fresh install.
    All I can say as advice is stay clear of the last “Details” option of the settings as it seams to trigger the problem.

  • The same problem with Mangaro Gnome:(

  • I do not have this issue on a installed gnome here…

    But looks like a BUG.

    https://bbs.archlinux.org/viewtopic.php?id=244792

  • @joekamprad As indicated in the link, downgrading package glib2-2.60.0-1 to glib2-2.58.3-1 immediately fixes the problem.
    Having a fresh installation I had to copy the old module from another computer.
    The bug arise with glib2-2.60.0-1 after you have selected “Details” in gnome-control-center.
    https://bugs.archlinux.org/task/61974?project=1&string=glib2

  • sudo pacman -U https://archive.archlinux.org/packages/g/glib2/glib2-2.58.3-1-x86_64.pkg.tar.xz
    

    I can confirm that downgrading fixes the problem.
    Be careful updating not to include glib.

    sudo pacman -Syyu --ignore glib2
    
crashing13 gnome-control-c1 Posts 9Views 379
Log in to reply
Bloom Email Optin Plugin

Looks like your connection to Antergos Community Forum was lost, please wait while we try to reconnect.