[Touch-packages] [Bug 1709649] Re: 229 backport for race between explicit mount and handling automount

Thanks for porting this to Xenial. Should the Xenial Ubuntu Base release be updated? The Ubuntu Base 16.04.3 does come with the problematic systemd, and on some systems, like the armhf, booting to a bare rootfs is impossible (always get the issue, which manifest itself as 'A start job is running

[Touch-packages] [Bug 1709649] Re: 229 backport for race between explicit mount and handling automount

Ok, I just tried with this version, and the issue I am seeing sadly does persist. So, this does not resolve it. Please ignore the last comment. Sorry, Eric -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in

[Touch-packages] [Bug 1835809] Re: AMD Ryzen 3000 series fails to boot

Good findings! Thank you so much for testing the rdrand theory. I guess a read fix would require a new ISO, which could easily be made as a dot release (19.04.1). Regards, Eric -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed

[Touch-packages] [Bug 1854314] Re: Legacy directory /var/run in /lib/systemd/system/dbus.socket

Same thing here ... Dec 1 06:42:11 lx-dev3 containerd[845]: time="2020-12-01T06:42:11.225821304-05:00" level=info msg="Stop CRI service" Dec 1 06:42:11 lx-dev3 containerd[845]: time="2020-12-01T06:42:11.242385111-05:00" level=info msg="Stop CRI service" Dec 1 06:42:11 lx-dev3