GNOME Bugzilla – Bug 788063
Segmentation fault on touchpad enabling/disabling
Last modified: 2017-09-26 12:19:56 UTC
While enabling (or disabling) the touchpad, I face this segfault: (gnome-control-center:16098): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion 'instance != NULL && instance->g_class != NULL' failed Segmentation fault This happens on Debian unstable/sid.
Created attachment 360302 [details] GDB backtrace Adding a backtrace of the same procedure.
Thanks for taking the time to report this. Without a full stack trace (which includes debug symbols) from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so. When pasting a stack trace in this bug report, please reset the status of this bug report from NEEDINFO to its previous status. Thanks in advance!
Created attachment 360307 [details] GDB with full backtrace As requested, a full backtrace of the segfault.
And I cannot reset status to previous status. No idea why.
That's still not a full stack trace with debugging symbols but it seems to have a matching pattern to the trace in bug 787897 . Can you try to get a better trace after installing debugging symbols to be sure?
(In reply to Rui Matos from comment #5) > That's still not a full stack trace with debugging symbols but it seems to > have a matching pattern to the trace in bug 787897 . Can you try to get a > better trace after installing debugging symbols to be sure? Well, I followed https://wiki.debian.org/HowToGetABacktrace#Advanced_gdb_commands with debug symbols installed from https://packages.debian.org/experimental/gnome-control-center-dbgsym No idea what I do more, sorry.
The stacktrace contains no calls to any code in gnome-control-center but to glib2 and libffi and libnm. Hence those are the things that need debug symbols. :) Also, using "thread apply all bt full" in gdb is welcome.
(In reply to André Klapper from comment #7) > The stacktrace contains no calls to any code in gnome-control-center but to > glib2 and libffi and libnm. Hence those are the things that need debug > symbols. :) > > Also, using "thread apply all bt full" in gdb is welcome. Oh perfect... gonna try later today. Thanks for the heads up.
Created attachment 360382 [details] GDB backtrace with glib2, libnm and libffi debug symbols installed
There is no stacktrace in that attachment. See https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details#Obtaining_a_stack_trace_using_GDB
Created attachment 360388 [details] Real GDB backtrace on all lib* required Oh, sorry for the mess... ;-) Should be ok now. Thanks for your patience.
Thanks! Pasting inline so the stacktrace parser can pick it up: Starting program: /usr/bin/gnome-control-center [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffcda40700 (LWP 27407)] [New Thread 0x7fffcd23f700 (LWP 27408)] [New Thread 0x7fffcca3e700 (LWP 27409)] [New Thread 0x7fffcbd57700 (LWP 27410)] [New Thread 0x7fffcb556700 (LWP 27411)] [New Thread 0x7fffcad55700 (LWP 27412)] [New Thread 0x7fffbb98d700 (LWP 27413)] [New Thread 0x7fffb9048700 (LWP 27416)] [New Thread 0x7fffb8847700 (LWP 27417)] [New Thread 0x7fffb3fff700 (LWP 27418)] [New Thread 0x7fffb37fe700 (LWP 27419)] [Thread 0x7fffb37fe700 (LWP 27419) exited] [Thread 0x7fffb9048700 (LWP 27416) exited] [Thread 0x7fffbb98d700 (LWP 27413) exited] [Thread 0x7fffb3fff700 (LWP 27418) exited] Thread 1 "gnome-control-c" received signal SIGSEGV, Segmentation fault. manager_recheck_permissions (proxy=<optimized out>, user_data=0x555555d59220) at libnm/nm-manager.c:363 363 libnm/nm-manager.c: No such file or directory.
+ Trace 238005
Thread 1 (Thread 0x7ffff7f5fac0 (LWP 27403))
Thanks, that definitely looks like bug 787897 . Update your NetworkManager packages when the fix reaches your distro. *** This bug has been marked as a duplicate of bug 787897 ***