Unable to update MX Linux: NO_PUBKEY A8580BDC82D3DC6C

Description of the issue:

I am unable to correctly update the Brave Browser package repository due to an invalid or missing key, specifically NO_PUBKEY A8580BDC82D3DC6C

How can this issue be reproduced?

  1. sudo apt-get update

Expected result:

Normal update of repository mirrors, specifically the one for the Brave Browser.

Brave Version( check About Brave):

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

Additional Information:

Operating system

This system is an MX Linux 64Bit O/S.

Relevant apt-get output

Err:6 https://brave-browser-apt-release.s3.brave.com trusty InRelease
The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A8580BDC82D3DC6C
Reading package lists… Done
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 trusty 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/trusty/InRelease The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A8580BDC82D3DC6C
W: Some index files failed to download. They have been ignored, or old ones used instead.

Remedies actioned

I have actioned two ‘fixes’ however the required repository/package keys are still invalid or not available.

Channel operators

I would have advised of the referring links for the 2 failed fixes, however as a new user, I can only post 4 links.

1 Like

This should be resolved. If you run apt update again, it should work this time.

The problem is that we accidentally used the wrong key (they one we are planning to switch to early next year) to sign the repository and so that’s why you saw that error message.

This topic was automatically closed after 30 days. New replies are no longer allowed.