Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

apt update via Ubuntu showing public key error

See original GitHub issue

Description

sudo apt update on Ubuntu 19.10 results in the following error:

Get:6 https://brave-browser-apt-release.s3.brave.com eoan InRelease [3,162 B]  
Err:6 https://brave-browser-apt-release.s3.brave.com eoan InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A8580BDC82D3DC6C


W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://brave-browser-apt-release.s3.brave.com eoan InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A8580BDC82D3DC6C
W: Failed to fetch https://brave-browser-apt-release.s3.brave.com/dists/eoan/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A8580BDC82D3DC6C

Steps to Reproduce

Open terminal
sudo apt update
See error

Actual result:

Get:6 https://brave-browser-apt-release.s3.brave.com eoan InRelease [3,162 B]  
Err:6 https://brave-browser-apt-release.s3.brave.com eoan InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A8580BDC82D3DC6C


W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://brave-browser-apt-release.s3.brave.com eoan InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A8580BDC82D3DC6C
W: Failed to fetch https://brave-browser-apt-release.s3.brave.com/dists/eoan/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A8580BDC82D3DC6C

Expected result:

No error, Brave should update

Reproduces how often:

I only have one Ubuntu machine available and can’t get around it so far

Brave version (brave://version info)

Version 1.0.1 Chromium: 78.0.3904.108 (Official Build) (64-bit)

Version/Channel Information:

Can you reproduce this issue with the current release? Yes
Can you reproduce this issue with the beta channel?
Can you reproduce this issue with the dev channel?
Can you reproduce this issue with the nightly channel?

Other Additional Information:

Does the issue resolve itself when disabling Brave Shields?
Does the issue resolve itself when disabling Brave Rewards?
Is the issue reproducible on the latest version of Chrome?

Miscellaneous Information:

Issue Analytics

State:
Created 4 years ago
Comments:12 (2 by maintainers)

Top GitHub Comments

6reactions

SQRedercommented, Aug 14, 2021

The solution was sudo chmod 644 /usr/share/keyrings/brave-browser-archive-keyring.gpg By some reason key was stored with 600 permissions, so apt just can’t read the content

2reactions

fmariercommented, Aug 14, 2021

@SQReder Did this step succeed?

sudo curl -fsSLo /usr/share/keyrings/brave-browser-archive-keyring.gpg https://brave-browser-apt-release.s3.brave.com/brave-browser-archive-keyring.gpg

Do you get the same output as me if you run the following?

$ md5sum /usr/share/keyrings/brave-browser-archive-keyring.gpg
54024f7bfef85749173de7ef859ca68b  /usr/share/keyrings/brave-browser-archive-keyring.gpg

Top Results From Across the Web

How do I fix the GPG error "NO_PUBKEY"? - Ask Ubuntu

Execute the following commands in terminal sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys <PUBKEY>. where <PUBKEY> is your missing public key ...

Fix apt-get update “the following signatures couldn't be ...

Fix apt-get update “the following signatures couldn't be verified because the public key is not available” The apt packaging system has a set...

Can't apt update due to key NO_PUBKEY error on ubuntu 18.04

The error message "The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8EC7C4A37DA6B9A9".

How to fix the apt-key deprecated warning in Ubuntu

How to solve the apt-key error the quick way · Open a terminal window. · Change into the apt directory with cd /etc/apt....

Problem with public key on apt-get update

The missing key is the key for the Samsung Unified Linux Driver Repository. Following the instructions added to the website yesterday should ...