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)
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
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