@Alfonso, right, but the details about what exactly failed is quite important/useful information. If some certificates are deemed invalid on boot until there is network this does not sound too bad at first. If this causes services to not start, then this becomes more important to fix. Also wondering how this works on different arches (like armhf/raspberrypi). Those things have no RTC and also no links to kernel/initrd in /. Those come up ok even with last mount time being off. But then maybe those do not run whatever is having issues.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1696981 Title: fixrtc is ineffective when there is no battery for the RTC Status in initramfs-tools package in Ubuntu: Incomplete Bug description: When there is no battery for the RTC, fixrtc is not able to find a good enough date. To fix the clock, this script is using the last time the root filesystem was mounted, but as that is done before there is any network, and as after a reboot/poweroff the RTC time is always reset (because time is not kept due to lack of battery), the mount time will never be good. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1696981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
