GNOME Bugzilla – Bug 782245
GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion 'instance != NULL && instance->g_class != NULL' failed
Last modified: 2017-05-07 16:16:50 UTC
Created attachment 351239 [details] 3 text logfiles from 3 system tools (gdb, term, systemd) Hello. With Manjaro Linux Gnome 64 bits, gnome-control-center crash after going back from network settings. Steps to systematically reproduce the bug on my machine : 1) Open g-c-c 2) Click on network 3) Click the back arrow of the title bar Find attached some logs. No extensions were loaded. Thank you for your work, gnome is IMO a polished and practical DE ! TL
Please paste the backtrace of the crash (the gdb output) directly in the comment field.
Here it is : GNU gdb (GDB) 7.12.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from gnome-control-center...(no debugging symbols found)...done. (gdb) run 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 0x7fffcda56700 (LWP 23299)] [New Thread 0x7fffcc9f7700 (LWP 23300)] [New Thread 0x7fffc7fff700 (LWP 23301)] [New Thread 0x7fffbffff700 (LWP 23302)] [New Thread 0x7fffbf7fe700 (LWP 23303)] (gnome-control-center:23295): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion 'instance != NULL && instance->g_class != NULL' failed Thread 1 "gnome-control-c" received signal SIGSEGV, Segmentation fault. 0x00007ffff2e70cd2 in ?? () from /usr/lib/libnm.so.0 (gdb) bt full
+ Trace 237426
Looks like bug 778615. Can you please add the necessary debuginfo packages to get a backtrace with more information? Or upgrade to a version of NetworkManager with that patch?
Thank you for this pointer. Here is some info : I followed your link and found that the patch you are referring to seems to have been applied to NetworkManager 1.6.x in late February. The point is that when I encountered this systematic bug, I was running 1.6.2-3 which is I think the last revision of the 1.6 version of NetworkManager. Nonetheless after upgrading NetworkManager to 1.9.0.r17590.g0461da269-1 (git version via aur repository), gnome-control-center is not crashing anymore. So I am not sure that the 1.6.x branch of nm is free of this bug but something definitely improved in the (at least) 1.9 version of nm. Anyway, thank you. TL
$ git describe 0429753dab39c245f280c47ee269d88cf92d7061 1.6.3-dev-23-g0429753da So it's not in 1.6.2. *** This bug has been marked as a duplicate of bug 778615 ***
Oh yeah nice, I spent time trying to get that info from the https://cgit.freedesktop.org/NetworkManager when I could have applied this neat command...
Don't change the status of the bug please. *** This bug has been marked as a duplicate of bug 778615 ***