same for me, it took me ages to figure out the root cause as I was
mislead by libcrypt failure messages at boot time
Start-Date: 2020-11-10 08:26:49
Commandline: aptdaemon role='role-commit-packages' sender=':1.82'
Install: libpam0g:i386 (1.3.1-5ubuntu4.1, automatic), libdevmapper1.02.1:i386
(2:1.02.167-1ubuntu1, automatic), libseccomp2:i386 (2.4.3-1ubuntu3.20.04.3,
automatic), libargon2-1:i386 (0~20171227-0.2, automatic), libsystemd0:i386
(245.4-4ubuntu3.3, automatic), gcc-10-base:i386 (10.2.0-5ubuntu1~20.04,
automatic), libacl1:i386 (2.2.53-6, automatic), libkmod2:i386 (27-1ubuntu2,
automatic), libmount1:i386 (2.34-0.1ubuntu9.1, automatic), libgpg-error0:i386
(1.37-1, automatic), libgmp10:i386 (2:6.2.0+dfsg-4, automatic), libc6:i386
(2.31-0ubuntu9.1, automatic), libudev1:i386 (245.4-4ubuntu3.3, automatic),
libapparmor1:i386 (2.13.3-7ubuntu5.1, automatic), libcrypt1:i386
(1:4.4.10-10ubuntu4, automatic), systemd-timesyncd:i386 (245.4-4ubuntu3.3,
automatic), libblkid1:i386 (2.34-0.1ubuntu9.1, automatic), libcap2:i386
(1:2.32-1, automatic), libuuid1:i386 (2.34-0.1ubuntu9.1, automatic),
libgcrypt20:i386 (1.8.5-5ubuntu1, automatic), libselinux1:i386 (3.0-1build2,
automatic), liblz4-1:i386 (1.9.2-2, automatic), libpcre2-8-0:i386 (10.34-7,
automatic), systemd:i386 (245.4-4ubuntu3.3, automatic), libhogweed5:i386
(3.5.1+really3.5.1-2, automatic), libgcc-s1:i386 (10.2.0-5ubuntu1~20.04,
automatic), libnettle7:i386 (3.5.1+really3.5.1-2, automatic), libcap-ng0:i386
(0.7.9-2.1build1, automatic), libgnutls30:i386 (3.6.13-2ubuntu1.3, automatic),
libffi7:i386 (3.3-4, automatic), libunistring2:i386 (0.9.10-2, automatic),
libp11-kit0:i386 (0.23.20-1build1, automatic), libcryptsetup12:i386
(2:2.2.2-3ubuntu2.3, automatic), libssl1.1:i386 (1.1.1f-1ubuntu2, automatic),
libtasn1-6:i386 (4.16.0-2, automatic), libjson-c4:i386 (0.13.1+dfsg-7ubuntu0.3,
automatic), liblzma5:i386 (5.2.4-1ubuntu1, automatic), libip4tc2:i386
(1.8.4-3ubuntu2, automatic), libidn2-0:i386 (2.2.0-2, automatic),
libaudit1:i386 (1:2.8.5-2ubuntu6, automatic)
Upgrade: netplan.io:amd64 (0.100-0ubuntu4~20.04.2, 0.100-0ubuntu4~20.04.3),
libsystemd0:amd64 (245.4-4ubuntu3.2, 245.4-4ubuntu3.3), udev:amd64
(245.4-4ubuntu3.2, 245.4-4ubuntu3.3), libudev1:amd64 (245.4-4ubuntu3.2,
245.4-4ubuntu3.3), systemd-sysv:amd64 (245.4-4ubuntu3.2, 245.4-4ubuntu3.3),
libpam-systemd:amd64 (245.4-4ubuntu3.2, 245.4-4ubuntu3.3), libnss-systemd:amd64
(245.4-4ubuntu3.2, 245.4-4ubuntu3.3), libnetplan0:amd64
(0.100-0ubuntu4~20.04.2, 0.100-0ubuntu4~20.04.3)
Remove: snapd:amd64 (2.47.1+20.04), plymouth-label:amd64
(0.9.4git20200323-0ubuntu6.1), plymouth-theme-ubuntu-text:amd64
(0.9.4git20200323-0ubuntu6.1), systemd-timesyncd:amd64 (245.4-4ubuntu3.2),
plymouth-theme-spinner:amd64 (0.9.4git20200323-0ubuntu6.1), systemd:amd64
(245.4-4ubuntu3.2), plymouth:amd64 (0.9.4git20200323-0ubuntu6.1),
dbus-user-session:amd64 (1.12.16-2ubuntu2.1)
End-Date: 2020-11-10 08:27:22
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903273
Title:
snapd automatically removed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1903273/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
