GNOME Bugzilla – Bug 778810
Control Center core dump
Last modified: 2017-03-10 18:15:01 UTC
Gnome Control Center: 3.22.1. Process 17727 (gnome-control-c) of user 1000 dumped core. Stack trace of thread 17727: #0 0x00007fbcba941cd2 n/a (libnm.so.0) #1 0x00007fbcba942379 n/a (libnm.so.0) #2 0x00007fbca72391c8 ffi_call_unix64 (libffi.so.6) #3 0x00007fbca7238c2a ffi_call (libffi.so.6) #4 0x00007fbcb842d7ae g_cclosure_marshal_generic (libgobject-2.0.so.0) #5 0x00007fbcb842cf75 g_closure_invoke (libgobject-2.0.so.0) #6 0x00007fbcb843ef82 n/a (libgobject-2.0.so.0) #7 0x00007fbcb8447bcc g_signal_emit_valist (libgobject-2.0.so.0) #8 0x00007fbcb844845b g_signal_emit_by_name (libgobject-2.0.so.0) #9 0x00007fbcb8745765 n/a (libgio-2.0.so.0) #10 0x00007fbcb8726344 n/a (libgio-2.0.so.0) #11 0x00007fbcb815443a g_main_context_dispatch (libglib-2.0.so.0) #12 0x00007fbcb81547f0 n/a (libglib-2.0.so.0) #13 0x00007fbcb815489c g_main_context_iteration (libglib-2.0.so.0) #14 0x00007fbcb870e54d g_application_run (libgio-2.0.so.0) #15 0x000000000044cff7 main (gnome-control-center) #16 0x00007fbcb7a88291 __libc_start_main (libc.so.6) #17 0x000000000044d19a _start (gnome-control-center) Stack trace of thread 17730: #0 0x00007fbcb7b4748d poll (libc.so.6) #1 0x00007fbcb8154786 n/a (libglib-2.0.so.0) #2 0x00007fbcb815489c g_main_context_iteration (libglib-2.0.so.0) #3 0x00007fbcb81548e1 n/a (libglib-2.0.so.0) #4 0x00007fbcb817c0d5 n/a (libglib-2.0.so.0) #5 0x00007fbcbb265454 start_thread (libpthread.so.0) #6 0x00007fbcb7b507df __clone (libc.so.6) Stack trace of thread 17792: #0 0x00007fbcb7b4748d poll (libc.so.6) #1 0x00007fbcb8154786 n/a (libglib-2.0.so.0) #2 0x00007fbcb815489c g_main_context_iteration (libglib-2.0.so.0) #3 0x00007fbc904934bd n/a (libdconfsettings.so) #4 0x00007fbcb817c0d5 n/a (libglib-2.0.so.0) #5 0x00007fbcbb265454 start_thread (libpthread.so.0) #6 0x00007fbcb7b507df __clone (libc.so.6) Stack trace of thread 17731: #0 0x00007fbcb7b4748d poll (libc.so.6) #1 0x00007fbcb8154786 n/a (libglib-2.0.so.0) #2 0x00007fbcb8154b12 g_main_loop_run (libglib-2.0.so.0) #3 0x00007fbcb873a316 n/a (libgio-2.0.so.0) #4 0x00007fbcb817c0d5 n/a (libglib-2.0.so.0) #5 0x00007fbcbb265454 start_thread (libpthread.so.0) #6 0x00007fbcb7b507df __clone (libc.so.6) Stack trace of thread 17793: #0 0x00007fbcb7b4bf19 syscall (libc.so.6) #1 0x00007fbcb819a03a g_cond_wait_until (libglib-2.0.so.0) #2 0x00007fbcb8128e89 n/a (libglib-2.0.so.0) #3 0x00007fbcb81294ac g_async_queue_timeout_pop (libglib-2.0.so.0) #4 0x00007fbcb817cb9d n/a (libglib-2.0.so.0) #5 0x00007fbcb817c0d5 n/a (libglib-2.0.so.0) #6 0x00007fbcbb265454 start_thread (libpthread.so.0) #7 0x00007fbcb7b507df __clone (libc.so.6) Stack trace of thread 17729: #0 0x00007fbcbb26b10f pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007fbca45654cc __gthread_cond_wait (libstdc++.so.6) #2 0x00007fbcb43e36bc _ZN7bmalloc9AsyncTaskINS_4HeapEMS1_FvvEE13threadRunLoopEv (libjavascriptcoregtk-4.0.so.18) #3 0x00007fbcb43e3809 _ZN7bmalloc9AsyncTaskINS_4HeapEMS1_FvvEE16threadEntryPointEPS4_ (libjavascriptcoregtk-4.0.so.18) #4 0x00007fbca456b58f execute_native_thread_routine (libstdc++.so.6) #5 0x00007fbcbb265454 start_thread (libpthread.so.0) #6 0x00007fbcb7b507df __clone (libc.so.6) Reproduce: * Open control center. * Click any icon. * Click '<' back button. * Click any icon. * Click '<' back button. * Repeat for a while.
Thanks for taking the time to report this. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so and reopen this bug report. Thanks in advance!
Deeper trace with gnome-control-panel (3.22.1) and network-manager (1.6.2) built with debug symbols on Antergos i.e. Arch. Starting program: /usr/bin/gnome-control-center [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0x7fffccb91700 (LWP 26984)] [New Thread 0x7fffcb9f7700 (LWP 26985)] [New Thread 0x7fffcb1f6700 (LWP 26986)] [New Thread 0x7fffc8983700 (LWP 26987)] [New Thread 0x7fffbb9f9700 (LWP 26988)] [New Thread 0x7fffbb1f8700 (LWP 26991)] [Thread 0x7fffbb9f9700 (LWP 26988) exited] Thread 1 "gnome-control-c" received signal SIGSEGV, Segmentation fault. handle_property_changed (self=self@entry=0x164d0d0, dbus_name=<optimized out>, value=<optimized out>) at libnm/nm-object.c:682 682 libnm/nm-object.c: No such file or directory.
+ Trace 237153
Thanks for taking the time to report this. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 778615 ***