Problem solved:
Booting the Ubuntu system the timedate service didn't work (bug?). The
date was one year behind. Therefore some certificates failed and thus
some connections to repositories.
I changed timedate to ntp and all works fine!
$ sudo timedatectl set-ntp no
$ sudo apt install ntp
Public bug reported:
Running ubuntu-20.04.2-preinstalled-server-arm64+raspi.img on a
Raspberry PI 3
After installation of the Ubuntu software updating apps and installing
new apps fail. Several repositories cannot be accessed because their
certificates aren't yet valid. The reason is that the 'ti
The workaround described only works only once, but not any more after
boot.
The reason is the missing service 'chrony' since the service 'ntp' isn't longer
supported by timedatectl. So the problem can be solved with:
$ sudo apt-get install chrony
$ sudo timedatectl set-ntp true
Th
Hi Paride,
I'm so sorry, but I cannot reproduce the problem.
In the last 2 weeks I setup my Raspberry PI3 about 20 times, always with
the same image. Booting the fresh installed system I got the problem
with the system clock. But after I could solve the problem it doesn't
appear again, even with
