Here is the output, though it looks even less verbose: sudo journalctl -u snapd -- Logs begin at Do 2016-02-11 16:28:01 UTC, end at Mi 2018-08-01 13:07:25 UTC. -- Aug 01 11:52:47 ubuntu systemd[1]: Starting Snappy daemon... Aug 01 11:52:48 ubuntu snapd[1045]: AppArmor status: apparmor is enabled and all features are availab Aug 01 11:52:48 ubuntu snapd[1045]: 2018/08/01 11:52:48.973342 daemon.go:343: started snapd/2.34.2 (s Aug 01 11:52:48 ubuntu systemd[1]: Started Snappy daemon. Aug 01 12:05:49 ubuntu snapd[1045]: 2018/08/01 12:05:49.362611 main.go:81: Exiting on terminated sign Aug 01 12:05:49 ubuntu systemd[1]: Stopping Snappy daemon... Aug 01 12:05:49 ubuntu systemd[1]: Stopped Snappy daemon. Aug 01 12:05:49 ubuntu systemd[1]: Starting Snappy daemon... Aug 01 12:05:49 ubuntu snapd[2902]: AppArmor status: apparmor is enabled and all features are availab Aug 01 12:05:49 ubuntu snapd[2902]: 2018/08/01 12:05:49.753958 daemon.go:343: started snapd/2.34.2 (s Aug 01 12:05:49 ubuntu systemd[1]: Started Snappy daemon. lines 1-12/12 (END)
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784843 Title: snap list: unexpected fault address 0xfffff1f0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1784843/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
