Hello! Thanks for maintaining snapd packages!
I recently got an upgrade of snapd on Ubuntu 20.10 Hirsute. I only use it for Chromium, mainly to attend some meetings. Chromium had been updated 12 days ago according to 'snap info'. It has been restarted since then. "lxd" has not been upgraded recently. After the upgrade, my microphone was not accepted in a meeting. I restarted chromium but nothing happened: it didn't restart. I quickly checked with "ps" and there was one process started and related to chromium: /snap/bin/chromium. Relaunching Chromium added one process like that. I also did: "snap list" but nothing was printed and it looked stuck, I didn't get the prompt back. Sadly, I didn't have time to investigate more because I was expected in a meeting so I did a Windows (reboot) and after it was OK. I didn't try to restart snapd services :-/ After the reboot (and the meeting), I tried to collect more logs: $ journalctl -u snapd -b-1 (...) Nov 29 21:26:46 me snapd[974]: storehelpers.go:551: cannot refresh: snap has no updates available: "chromium", "core", "core18", "core20", "gtk-common-themes" (...) Nov 30 10:43:48 me systemd[1]: Stopping Snap Daemon... Nov 30 10:43:48 me snapd[974]: main.go:155: Exiting on terminated signal. Nov 30 10:44:13 me snapd[974]: daemon.go:586: WARNING: cannot gracefully shut down in-flight snapd API activity within: 25s Nov 30 10:45:18 me systemd[1]: snapd.service: State 'stop-sigterm' timed out. Killing. Nov 30 10:45:18 me systemd[1]: snapd.service: Killing process 974 (snapd) with signal SIGKILL. Nov 30 10:45:18 me systemd[1]: snapd.service: Main process exited, code=killed, status=9/KILL Nov 30 10:45:18 me systemd[1]: snapd.service: Failed with result 'timeout'. Nov 30 10:45:18 me systemd[1]: Stopped Snap Daemon. Nov 30 10:45:18 me systemd[1]: snapd.service: Triggering OnFailure= dependencies. $ journalctl -u snapd.apparmor -b-1 -- Logs begin at Mon 2020-10-12 09:26:32 CEST, end at Mon 2020-11-30 12:08:22 CET. -- Nov 27 10:41:38 me systemd[1]: Starting Load AppArmor profiles managed internally by snapd... Nov 27 10:41:38 me systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Nov 30 10:43:48 me systemd[1]: snapd.apparmor.service: Succeeded. Nov 30 10:43:48 me systemd[1]: Stopped Load AppArmor profiles managed internally by snapd. $ journalctl -u snapd.seeded.service -b-1 -- Logs begin at Mon 2020-10-12 09:26:32 CEST, end at Mon 2020-11-30 12:08:52 CET. -- Nov 27 10:41:39 me systemd[1]: Starting Wait until snapd is fully seeded... Nov 27 10:41:39 me systemd[1]: Finished Wait until snapd is fully seeded. Nov 30 10:43:48 me systemd[1]: snapd.seeded.service: Succeeded. Nov 30 10:43:48 me systemd[1]: Stopped Wait until snapd is fully seeded. $ journalctl -u snapd.failure -b-1 -- Logs begin at Mon 2020-10-12 09:26:32 CEST, end at Mon 2020-11-30 12:08:52 CET. -- Nov 30 10:45:18 me systemd[1]: Starting Failure handling of the snapd snap... Nov 30 10:45:18 me systemd[1]: snapd.failure.service: Succeeded. Nov 30 10:45:18 me systemd[1]: Finished Failure handling of the snapd snap. Not sure it would help. I didn't find any logs related to snapd in /var/log. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904098 Title: [SRU] 2.48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1904098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
