Thank you for your bug report. Do you have specific steps that trigger the issue? Could you add the 'journalctl -b <n>' from a session where you got the issue (n = 1 probably if you restarted once since you got the issue)
Could you also try to get a backtrace by following https://wiki.ubuntu.com/Backtrace ? The apport service should catch those issues but doesn't at the moment because of bug #1870060 , one workaround is to comment the ProtectSystem line from the systemd .service and restart, then apport should catch the segfault ** Changed in: network-manager (Ubuntu) Importance: Undecided => High ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888648 Title: network-manager crashes: "NetworkManager needs to be running" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1888648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
