Adding the anbox repository gives me these weird issues. i used the --allow-insecure-repositories but that only works for my update Please help.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://ppa.launchpad.net/jconti/gnome3/ubuntu groovy Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://ppa.launchpad.net/morphis/anbox-support/ubuntu groovy Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://ppa.launchpad.net/peppermintos/p9-release/ubuntu groovy Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://deb.fdmpkg.org bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 38832685B6D09383
E: The repository 'http://deb.fdmpkg.org bionic InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.```
... does not have a Release filemessages, this typically means that the PPA doesn't offer packages for your version of Ubuntu. For example,https://launchpad.net/~jconti/+archive/ubuntu/gnome3is only available up to Raring Ringtail, which is from 2013. For newer Ubuntu releases, you need to look for a different PPA that offers packages for the release you use (probably Groovy Gorilly from last October). – Henning Kockerbeck Mar 12 '21 at 12:33... The following signatures couldn't be verified because the public key is not available...messages, those repos are signed with a public / private key combination. You need to get the public key, soaptcan verify the signature. You'll want to look into theapt-keycommand (and maybe public / private keys in general). – Henning Kockerbeck Mar 12 '21 at 12:35