The latest firefox-bin update fails to complete due to an unrecognized key:
…
Building firefox-bin…
==> Making package: firefox-bin 154.0-1 (Wed 19 Aug 2026 05:50:22 SAST)
==> Checking runtime dependencies…
==> Checking buildtime dependencies…
==> Retrieving sources…
→ Found firefox.sh
→ Found firefox.desktop
→ Found policies.json
→ Found firefox-154.0-x86_64.tar.xz
→ Found firefox-154.0-x86_64.tar.xz.asc
==> Validating source files with sha256sums…
firefox.sh … Passed
firefox.desktop … Passed
policies.json … Passed
==> Validating source_x86_64 files with sha256sums…
firefox-154.0-x86_64.tar.xz … Passed
firefox-154.0-x86_64.tar.xz.asc … Skipped
==> Verifying source file signatures with gpg…
firefox-154.0-x86_64.tar.xz … FAILED (unknown public key 678E455D76767AA3)
==> ERROR: One or more PGP signatures could not be verified!
Failed to build firefox-bin
ERROR: One or more PGP signatures could not be verified!; what should I do?
Most likely, you do not have the required public key(s) in your personal keyring to verify downloaded files. See Makepkg#Signature checking for details.
AUR (en) - firefox-bin Alad commented on 2022-03-28 13:05 (UTC)
These are binaries from upstream built in a different way, with different dependencies. For example, it is statically linked and has a hard dependency on pulseaudio for sound support.
Seems the default ubuntu keyserver does not have this key. I guess one should not rely too much on Canonical :
[teo@teo-lenovo-v15 ~]$ gpg --keyserver hkps://keyserver.ubuntu.com --search-keys 678E455D76767AA3
gpg: data source: https://185.125.188.27:443
gpg: key "678E455D76767AA3" not found on keyserver
gpg: keyserver search failed: Not found
[teo@teo-lenovo-v15 ~]$ gpg --keyserver hkps://keys.openpgp.org --search-keys 678E455D76767AA3
gpg: data source: https://keys.openpgp.org:443
(1) Mozilla Software Releases <release@mozilla.com>
4096 bit RSA key 61B7B526D98F0353, created: 2015-07-17
Keys 1-1 of 1 for "678E455D76767AA3". Enter number(s), N)ext, or Q)uit > q
The solution is to change the server in gpg.conf pacman/system wide or to import the key to local store. Hint: in Seahorse one can even do this in the gui.
p.s. i fail to understand one would anyone want an aur variant of the same version that is in the repos (yeah i know it is slightly different technically but still )…
Agreed. I am unable to think of a good reason to use the AUR version unless there were extra needed features not available via the repository version. ← @joseheitor The latter is kept up to date, by the way.
Thanks Teo. Your solution was simple, clear and effective.
Wow - what a vibrant community!
Thanks for all the suggestions. As to why I use the AUR version of Firefox - perhaps it is unwarranted, but a previous update of the official build once lost my profiles and open tabs, which caused considerable mayhem, so I have since been using the AUR version, in hope that it does not do the same thing.
Mod edit:Consecutive posts merged, @mention added..
This is exactly what attracted me here in the first place, and I’ve certainly never regretted it.
I first moved over when the Mint team decided to drop Plasma aand also I liked the idea of a rolling-release without all that reinstallation or “risky upgrading” like you have with a point-release, but I needed a quick, stable fix rather than going straight to Arch and Manjaro fit the bill then, and still does, and as far as I can see it always will.
You’ll see I did merge your posts though as a bit of housekeeping. (I wish I could say the same about my humble abode). It is normally preferable to add extra info to an existing post if there are no intervening replies as this helps to avoid looooong threads.