Error http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: Key is stored in legacy

[btindie]

$ wget -qO- http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease | sudo tee /etc/apt/trusted.gpg.d/jammy-security.asc

That file you've downloaded is not a GPG key, hence the errors you're seeing. So please delete it.

sudo rm /etc/apt/trusted.gpg.d/jammy-security.asc

I'm not sure how you updated your system but I suspect you may be missing the supplied gpg keys that are in the ubuntu-keyring package.

What's in your /etc/apt/trusted.gpg.d directory?

ls -l /etc/apt/trusted.gpg.d

You can see the files in it at https://packages.ubuntu.com/jammy/ubuntu-keyring

That packages postinst script does:

if [ "$1" = 'configure' -a -n "$2" ]; then    # remove keys from the trusted.gpg file as they are now shipped in fragment files in trusted.gpg.d
    if dpkg --compare-versions "$2" 'lt' "2016.09.19" && which gpg > /dev/null && which apt-key > /dev/null; then
        TRUSTEDFILE='/etc/apt/trusted.gpg'
        eval $(apt-config shell TRUSTEDFILE Apt::GPGV::TrustedKeyring)
        eval $(apt-config shell TRUSTEDFILE Dir::Etc::Trusted/f)
        if [ -e "$TRUSTEDFILE" ]; then
            for KEY in 40976EAF437D05B5 46181433FBB75451 3B4FE6ACC0B21F32 D94AA3F0EFE21092; do
                apt-key --keyring "$TRUSTEDFILE" del $KEY > /dev/null 2>&1 || :
            done
        fi
    fi
fi

which is essentially what you did earlier.

It also contains the GPG keys for that release.

If you manually download that package https://packages.ubuntu.com/jammy/al...yring/download

Then install the downloaded file, that should add the missing GPG keys. e.g.

sudo apt-get install --reinstall ./Downloads/ubuntu-keyring_2021.03.26_all.deb

You need to prefix the path/filename with ./ so it knows to treat it as a local file.

The missing key with ID 871920D1991BC93C is in /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg in that package.

[tellapu]

Thank you, ActionParsnip, for your response!

[tellapu]

Thanks a lot, btindie, for all the instructions. It has been really busy here but I hope to be able to have some spare time next week as I really want to fix this.

A quick response at least to your question:

$ ls -l /etc/apt/keyring.d
ls: cannot access '/etc/apt/keyring.d': No such file or directory
$ ls -l /etc/apt/keyrings
total 4
-rw-r--r-- 1 root root 3147 Feb  2 12:00 teams-for-linux.asc

[tellapu]

No output or error with sudo ..../tmp/clean2.sh

I downloaded ubuntu-keyring_2021.03.26_all.deb.

$sudo apt-get install --reinstall ./.../ubuntu-keyring_2021.03.26_all.deb
E: Unsupported file ./media/Storage/tmp/ubuntu-keyring_2021.03.26_all.deb given on commandline

I tried then with GDebi but it gives the error "no longer provides ubuntu-keyring".

In the Synaptic app I found the package and marked it for "reinstall". This worked and afterwards, I got no error anymore:

$ sudo apt update
Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Get:2 http://download.opensuse.org/repositories/home:/ungoogled_chromium/Ubuntu_Jammy  InRelease [1,559 B]
Get:3 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]                 
Hit:4 https://download.virtualbox.org/virtualbox/debian jammy InRelease     
Hit:5 https://repo.teamsforlinux.de/debian stable InRelease                    
Get:6 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]        
Get:7 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB]
Get:8 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages [400 kB]
Get:9 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages [567 kB]
Get:10 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages [1,142 kB]
Get:11 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1,366 kB]
Get:12 http://security.ubuntu.com/ubuntu jammy-security/main Translation-en [211 kB]        
Get:13 http://security.ubuntu.com/ubuntu jammy-security/universe i386 Packages [590 kB]          
Get:14 http://archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [272 kB]               
Get:15 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 Packages [839 kB]         
Get:16 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1,044 kB]          
Get:17 http://security.ubuntu.com/ubuntu jammy-security/universe Translation-en [160 kB]                                                                                                                    
Get:18 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages [1,366 kB]                                                                                                                
Get:19 http://archive.ubuntu.com/ubuntu jammy-updates/universe i386 Packages [687 kB]                                                                                                                       
Get:20 http://archive.ubuntu.com/ubuntu jammy-updates/universe Translation-en [235 kB]                                                                                                                      
Get:21 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [1,412 kB]                                                                                                                  
Get:22 http://security.ubuntu.com/ubuntu jammy-security/restricted Translation-en [224 kB]                                                                                                                  
Get:23 http://archive.ubuntu.com/ubuntu jammy-updates/restricted Translation-en [233 kB]                                                                                                                    
Get:24 http://archive.ubuntu.com/ubuntu jammy-backports/universe i386 Packages [13.4 kB]                                                                                                                    
Get:25 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages [24.3 kB]                                                                                                                   
Fetched 11.1 MB in 14s (822 kB/s)                                                                                                                                                                           
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
5 packages can be upgraded. Run 'apt list --upgradable' to see them.

Hallelujah! I now have to work on all the PPAs and learn how to move them to /etc/apt/trusted.gpg.d/. But I guess ActionParsnip's link will help with this.
Thanks again so much for all your help!!!

[btindie]

A quick response at least to your question:

$ ls -l /etc/apt/keyring.d
ls: cannot access '/etc/apt/keyring.d': No such file or directory
$ ls -l /etc/apt/keyrings
total 4
-rw-r--r-- 1 root root 3147 Feb  2 12:00 teams-for-linux.asc

Sorry, I had meant to say

ls -l /etc/apt/trusted.gpg.d

On a clean docker image of ubuntu:22.04 it contains just

root@6eed3a8b0a0f:~# ls -l /etc/apt/trusted.gpg.dtotal 8
-rw-r--r-- 1 root root 2794 Mar 26  2021 ubuntu-keyring-2012-cdimage.gpg
-rw-r--r-- 1 root root 1733 Mar 26  2021 ubuntu-keyring-2018-archive.gpg

which are the gpg keys contained in that deb package. That's where you need to place the keys from your PPA's.

[tellapu]

Thank you!

The list in /etc/apt/trusted.gpg.d is long, I guess the previously done work has already helped.

But I am suprised that I have two Vivaldi-keys:
-rw-r--r-- 1 root root 2285 Feb 11 09:48 vivaldi-33EAAB8E.gpg
-rw-r--r-- 1 root root 2285 Feb 11 09:48 vivaldi-4218647E.gpg

Probably I could delete one at some stage. How to find out which one?

[tellapu]

Interestingly /usr/share/keyrings/ includes Ubuntu-Pro-Keys. Why would Ubuntu add them there in Nov 2023 as it is depreciated?

$ ls -l /usr/share/keyrings/
total 84
-rw-r--r-- 1 root root 4037 Oct 31 14:13 brave-browser-archive-keyring.gpg
-rw-r--r-- 1 root root 2462 Jun  8  2023 brave-browser-beta-archive-keyring.gpg
-rw-r--r-- 1 root root 2462 Jun  8  2023 brave-browser-nightly-archive-keyring.gpg
-rw-r--r-- 1 root root 2247 Jan  6  2023 oracle-virtualbox-2016.gpg
-rw-rw-r-- 1 cds  cds  2223 May  5  2021 signal-desktop-keyring.gpg
-rw-r--r-- 1 root root 7399 Sep 18  2018 ubuntu-archive-keyring.gpg
-rw-r--r-- 1 root root 6713 Oct 27  2016 ubuntu-archive-removed-keys.gpg
-rw-r--r-- 1 root root 3023 Mar 27  2021 ubuntu-cloudimage-keyring.gpg
-rw-r--r-- 1 root root    0 Jan 17  2018 ubuntu-cloudimage-removed-keys.gpg
-rw-r--r-- 1 root root 1227 May 27  2010 ubuntu-master-keyring.gpg
-rw-r--r-- 1 root root 1150 Nov  7 15:23 ubuntu-pro-anbox-cloud.gpg
-rw-r--r-- 1 root root 2247 Nov  7 15:23 ubuntu-pro-cc-eal.gpg
-rw-r--r-- 1 root root 2274 Nov  7 15:23 ubuntu-pro-cis.gpg
-rw-r--r-- 1 root root 2236 Nov  7 15:23 ubuntu-pro-esm-apps.gpg
-rw-r--r-- 1 root root 2264 Nov  7 15:23 ubuntu-pro-esm-infra.gpg
-rw-r--r-- 1 root root 2275 Nov  7 15:23 ubuntu-pro-fips.gpg
-rw-r--r-- 1 root root 2275 Nov  7 15:23 ubuntu-pro-fips-preview.gpg
-rw-r--r-- 1 root root 2250 Nov  7 15:23 ubuntu-pro-realtime-kernel.gpg
-rw-r--r-- 1 root root 2235 Nov  7 15:23 ubuntu-pro-ros.gpg

Unfortunately these keys don't appear with sudo apt-key list. At the end of the list I get this error:

W: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file has an unsupported filetype.

How to find out which one is the unsupported one?
Maybe the ubuntu-cloudimage-removed-keys.gpg as its size is 0?
Could I just delete it?
And the Brave-keyrings as a Brave-PPA is not listed in the "Other Software" in "Software & Updates"?

[tellapu]

In case somebody will read this in the future, I will answer the questions.

> But I am suprised that I have two Vivaldi-keys.
> Probably I could delete one at some stage. How to find out which one?

I think Vivaldi adds two keys by default and therefore it is best to not delete any.


> W: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file has an unsupported filetype.
> How to find out which one is the unsupported one?

As far as I can tell the trusted.gpg-file had a problem. When I deleted it, the error did not occur anymore.

From there, I added the PPA (I still needed) manually again. For a few PPAs/repositories I had to use the mentioned instructions:
https://www.omgubuntu.co.uk/2022/06/...rror-on-ubuntu
https://askubuntu.com/questions/1398...n-legacy-trust

Again, thank you very much, btindie, you made a big difference!

[caterhamfan]

Sorry for the bump.

I'm encountering a similar issue here

Main error:

E: Conflicting values set for option Signed-By regarding source https://ppa.launchpadcontent.net/yan...repair/ubuntu/ noble: /etc/apt/keyrings/boot-repair.gpg !

I have tried opening /etc/apt/sources.list and sudo nano /etc/apt/keyrings/boot-repair.gpg both are blank.

Be grateful for any assistance you can provide.

Thank you

[tellapu]

I am sorry to hear that you have this problem, @caterhamfan
Unfortunately, I don't have any tips either. Maybe @btindie can help.
I recommend to post the main error in your initial thread in order for people to see it straightaway and it can be found with a search function.
Hopefully you will find a solution for the problem! (If you do, thanks in advance for posting it in your thread.)