GNOME Bugzilla – Bug 788648
Settings app crashes when opening a VPN entry's settings
Last modified: 2017-10-08 16:30:18 UTC
Pressing the little menu icon (icon with 3 horizontal stripes) sometimes crashes the settings app (about 70% of the time I would say). Doesn't depend on whether or not the selected VPN was turned on or not. Console log when crash occurs: (gnome-control-center:22769): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion 'instance != NULL && instance->g_class != NULL' failed (gnome-control-center:22769): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed fish: “gnome-control-center” terminated by signal SIGSEGV (Address boundary error) Running Gnome 3.26.1 on Arch Linux.
Actually, I don't think I've managed to open up the VPN settings dialogue with the VPN turned off. So: when turned off, always crashes, when turned on, crashes most of the time.
Thanks for taking the time to report this. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace with debug symbols? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so. Thanks in advance!
Hmm, I'm afraid I might need a bit of help with the debugging process :D So I got the following stack trace:
+ Trace 238025
Thread 1 (Thread 0x7ffff7f3aa00 (LWP 2112))
Now GDB gave me this when the app crashed: Thread 1 "gnome-control-c" received signal SIGSEGV, Segmentation fault. 0x00007ffff2d54ca7 in ?? () from /usr/lib/libnm.so.0 As far as I understand, those two questionmarks indicate that I haven't enabled debugging support for libnm. libnm is part of the networkmanager package, so I downlaoded its sources, set the debug flags in its packagebuild, compiled and installed it, checked with GDB that the debug symbols weren't erased, yet it still shows those 2 question marks when crashing the settings app. I'm guessing I'm missing something, and that debug flags for libnm need to be set somewhere else, but I don't know where :/ Any help would be appreciated! :)
Nevermind, I'm an idiot :D I had installed the compiled networkmanager package, but didn't notice that I had also generated two libnm packages to install *faceplam* Anyway, here is the stack trace (finally :D)
+ Trace 238026
Thread 1 (Thread 0x7ffff7f3aa00 (LWP 2690))
Hopefully this helps find the bug :)
looks like bug 787893 . re-open if it still happens after updating NM to a version that includes the fix *** This bug has been marked as a duplicate of bug 787893 ***