I believe I'm also having this problem. I've uploaded the whoopsie dump with apport but I can't see where it is being tracked (see http://askubuntu.com/questions/900191/where-do-i-look-to-see-if-my- whoopsie-is-being-tracked).
The stack looks the same: SegvAnalysis: Segfault happened at: 0x7fc79f90e830 <__libc_start_main+240>: mov %eax,%edi PC (0x7fc79f90e830) ok source "%eax" ok destination "%edi" ok SP (0x7ffc12fba2c0) ok Reason could not be automatically determined. SourcePackage: network-manager Stacktrace: #0 0x000000000048cc66 in nm_dns_manager_end_updates () #1 0x00007fc79d566e40 in ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 #2 0x00007fc79d5668ab in ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 #3 0x00007fc7a01f5cf5 in g_cclosure_marshal_generic_va () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #4 0x00007fc7a01f51d4 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x00007fc7a020f9a6 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x00007fc7a021008f in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 This started happening when I commented out the dns=dnsmasq line in my NetworkManager.conf and indeed the crash happens in DNS related code. The often occurs after resuming from suspend, but not always - it may also just occur while using the host. Here's a link to the whoopise upload - I don't have perms to see it, but perhaps someone who does can associate it with this bug? https://errors.ubuntu.com/oops/f3ce1fb0-1957-11e7-968c-fa163e8d4bab -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622571 Title: NetworkManager crashed with SIGSEGV in nm_dns_manager_end_updates() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1622571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
