Error: GPG check FAILED

Browser Support Desktop Support
1

Description of the issue:
Can’t install brave on Fedora 31.

Steps to Reproduce (add as many as necessary): 1. 2. 3.
I followed the steps at https://brave-browser.readthedocs.io/en/latest/installing-brave.html#linux but get the error Error: GPG check FAILED

Actual Result (gifs and screenshots are welcome!):
Public key for brave-browser-1.2.43-1.x86_64.rpm is not installed
Public key for brave-keyring-1.7-1.noarch.rpm is not installed
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing ‘dnf clean packages’.
Error: GPG check FAILED

Expected result:
Installing brave!
Reproduces how often:

Operating System and Brave Version(See the About Brave page in the main menu):
Fedora 31. Brave installed and ran fine in Fedora 30.

Additional Information:
I tried dnf clean packages with no success.

2

@arman1,
Thank you for reaching out. Can you try entering the following command to retrieve the correct and most up to date keyring?

sudo apt-get update && sudo apt-get install -y --only-upgrade brave-browser brave-keyring
1 Like
3

I’m on Fedora 31, so can’t use those commands. I did follow the fedora section of https://brave-browser.readthedocs.io/en/latest/installing-brave.html#linux with no success

4

Hey arman1,

That error might be due to not importing the GPG key to the RPM db first. Please try running all these instructions in series:

sudo dnf config-manager --add-repo https://brave-browser-rpm-release.s3.brave.com/x86_64/

sudo rpm --import https://brave-browser-rpm-release.s3.brave.com/brave-core.asc

sudo dnf install brave-browser
1 Like
5

Downloading Packages:
[SKIPPED] brave-browser-1.2.43-1.x86_64.rpm: Already downloaded
[SKIPPED] brave-keyring-1.7-1.noarch.rpm: Already downloaded
[SKIPPED] libindicator-gtk3-12.10.1-16.fc31.x86_64.rpm: Already downloaded
[SKIPPED] libappindicator-gtk3-12.10.0-25.fc31.x86_64.rpm: Already downloaded
[SKIPPED] libdbusmenu-16.04.0-14.fc31.x86_64.rpm: Already downloaded
[SKIPPED] libdbusmenu-gtk3-16.04.0-14.fc31.x86_64.rpm: Already downloaded
[SKIPPED] liberation-fonts-2.00.5-6.fc31.noarch.rpm: Already downloaded
warning: /var/cache/dnf/brave-browser-rpm-release.s3.brave.com_x86_64_-d55d330619c02b48/packages/brave-browser-1.2.43-1.x86_64.rpm: Header V4 RSA/SHA512 Signature, key ID 82d3dc6c: NOKEY
Public key for brave-browser-1.2.43-1.x86_64.rpm is not installed
Public key for brave-keyring-1.7-1.noarch.rpm is not installed
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing ‘dnf clean packages’.
Error: GPG check FAILED

6

One thing I should add - I did “dnf remove brave” before upgrading to Fedora 31 from Fedora 30 because there was a GPG related error preventing me from upgrading

7

What do you get if you run this as root:

rpm -q gpg-pubkey --qf '%{NAME}-%{VERSION}-%{RELEASE}\t%{SUMMARY}\n'

Do you have these?

gpg-pubkey-3c3359c4-5c6ae44d    Fedora (31) <[email protected]> public key
gpg-pubkey-c2d4e821-5e22514c    Brave Software <[email protected]> public key
8

Same issue: I ran the commands and get the following related to Brave and Fedora (google left out)

gpg-pubkey-cfc659b9-5b6eac67 gpg(Fedora (30) [email protected])
gpg-pubkey-c2d4e821-5d13a788 gpg(Brave Software [email protected])
gpg-pubkey-3c3359c4-5c6ae44d Fedora (31) [email protected] public key

9

Ok, so you have the wrong key for Brave. This is what you have:

gpg-pubkey-c2d4e821-5d13a788

and this is what you should have:

gpg-pubkey-c2d4e821-5e22514c

So do this to remove the old key:

sudo rpm -e gpg-pubkey-c2d4e821-5d13a788

and then you should be able to import the correct key using:

sudo rpm --import https://brave-browser-rpm-release.s3.brave.com/brave-core.asc
10

Thank you for this information!

I have successfully installed and it works as expected.

Thanks again.

11

Worked for me! Thanks a bunch… I missed brave this past week <3

12

A had a similar case when Cisco blacklisted Brave when it got the Tor capability. Apt started to complain the Brave package repository was unsigned all of sudden. Because it couldn’t find the repository’s public (GPG) key. This is a misleading error message.

What really happened is that Cisco Umbrella sent the request to a different ip address, because brave.com was blacklisted. And of course Apt can not find a public key on that address.

Simply open brave.com to see if you are blocked. If that’s the case you’ll have to argue with the sysadmins to lift the ban. I could convince them:

  1. Other browsers get the very same functionality with Tor extensions. And yet they are not blacklisted.
  2. I wouldn’t get very far anyway with Tor in Brave because Tor is blacklisted too.

Ergo: Blacklisting Brave made no sense.

13

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