I recently encountered a public key error while using Brave Browser on Linux Mint 22.2. The message indicated that certain packages could be upgraded, but it failed with a GPG error stating that the signatures couldn't be verified due to a missing public key (NO_PUBKEY 0686B78420038257). It mentioned that some index files failed to download, and I had to use AI to resolve it, which included manually adding the repository again and deleting the old one. Have others experienced this issue and what could be the root cause?
4 Answers
The "signature verification error" you encountered usually means that the GPG key for the software repository is either missing, expired, or invalid. It's a pretty common issue when using third-party PPAs or repos if you haven’t updated the keyring or if the key was removed from the server.
I faced the same issue just a few days ago! I couldn't find a proper fix, so I backed up my bookmarks and passwords before doing a complete removal of Brave using the apt purge command. After that, I ran a bash one-liner to reinstall Brave, and thankfully, the error disappeared without losing my saved info.
Just to clarify, I'm not sure why the error happened in the first place.
Is it something like this?
`curl -fsS https://dl.brave.com/install.sh | sh`
I ran two commands from an earlier thread, and it seems to have resolved my issue. It's worth checking out any solutions shared by the community!
I'm dealing with this issue right now too and looking for a fix. If I find out anything, I'll be sure to share it!
What was that bash one-liner? I assume it's different from just uninstalling and reinstalling the browser, right?