Page 2 of 2 FirstFirst 12
Results 11 to 18 of 18

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

  1. #11
    Join Date
    Jul 2009
    Beans
    516
    Distro
    Ubuntu 16.04 Xenial Xerus

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

    Code:
    $ 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.
    Code:
    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?
    Code:
    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:
    Code:
    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.
    Code:
    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.
    Last edited by btindie; February 11th, 2024 at 12:06 AM. Reason: Fix mistake
    Mark your thread as [SOLVED], use Thread Tools on forum page.

  2. #12
    Join Date
    Oct 2009
    Beans
    111
    Distro
    Ubuntu

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

    Thank you, ActionParsnip, for your response!

  3. #13
    Join Date
    Oct 2009
    Beans
    111
    Distro
    Ubuntu

    Cool Re: Error http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: Key is stored in le

    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:
    Code:
    $ 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

  4. #14
    Join Date
    Oct 2009
    Beans
    111
    Distro
    Ubuntu

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

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

    I downloaded ubuntu-keyring_2021.03.26_all.deb.

    Code:
    $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:

    Code:
    $ 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!!!

  5. #15
    Join Date
    Jul 2009
    Beans
    516
    Distro
    Ubuntu 16.04 Xenial Xerus

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

    Quote Originally Posted by tellapu View Post
    A quick response at least to your question:
    Code:
    $ 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
    Code:
    ls -l /etc/apt/trusted.gpg.d
    On a clean docker image of ubuntu:22.04 it contains just
    Code:
    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.
    Mark your thread as [SOLVED], use Thread Tools on forum page.

  6. #16
    Join Date
    Oct 2009
    Beans
    111
    Distro
    Ubuntu

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

    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?

  7. #17
    Join Date
    Oct 2009
    Beans
    111
    Distro
    Ubuntu

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

    Interestingly /usr/share/keyrings/ includes Ubuntu-Pro-Keys. Why would Ubuntu add them there in Nov 2023 as it is depreciated?
    Code:
    $ 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:
    Code:
    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"?

  8. #18
    Join Date
    Oct 2009
    Beans
    111
    Distro
    Ubuntu

    Red face Re: Error http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: Key is stored in le

    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!

Page 2 of 2 FirstFirst 12

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •