@tjhexf The PGP key is not outdated. Maybe there is some problem within your key server so you could try importing the key manually:

gpg --keyserver hkps://keys.openpgp.org --recv-keys 14F26682D0916CDD81E37B6D61B7B526D98F0353

as @aag said.

Thanks @Sving1024 and @VitalyR, the automated updates work great on aarch64 now!

@zrhoffman Thanks. Now we have separate arrays for sha512sums_x86_64and sha512sums_aarch64. The pkgbuild should be able to build on aarch64 arch now.

Ever since the Firefox sha512 started being checked in 8e63c12c40, the validity check has failed on aarch64:

$ makepkg
==> Making package: firefox-nightly-bin 152.0a1.20260511.160144-1 (Tue 12 May 2026 04:07:45 AM MDT)
==> Retrieving sources...
  -> Found firefox-nightly.desktop
  -> Found policies.json
  -> Found 20260511-160144-firefox-152.0a1.en-US.linux-aarch64.tar.xz
  -> Found 20260511-160144-firefox-152.0a1.en-US.linux-aarch64.tar.xz.asc
==> Validating source files with sha512sums...
    firefox-nightly.desktop ... Passed
    policies.json ... Passed
    20260511-160144-firefox-152.0a1.en-US.linux-aarch64.tar.xz ... FAILED
    20260511-160144-firefox-152.0a1.en-US.linux-aarch64.tar.xz.asc ... Skipped
==> ERROR: One or more files did not pass the validity check!

This is because it's checking the aarch64 archive against the x86_64 checksum. Now that the sha512 is an actual hash instead of SKIP, there should be separate arrays for sha512sums_x86_64 and sha512sums_aarch64.

For reference, the PKGBUILD updates now seem to be coming from the GitHub Actions workflow at https://github.com/Sving1024/PKGBUILD/blob/da00f7751d/.github/workflows/upd-ff-i18n.yaml#L46.

For those who could not import the key in any way due to an error "gpg: keyserver receive failed: Operation not permitted":

curl -s "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0xD98F0353" | gpg --import

@Sving1024 Thanks for the clarification, the master key stays unchanged indeed.

@NoSohoth the master key is not outdated at all. please manually update your key.

Please update the PKGBUILD to reflect Mozilla's new GPG key : 09BEED63F3462A2DFFAB3B875ECB6497C1A20256.

I was able to set default profile by going to about:profiles and setting my old profile as the default one

@mykiwi, it's likely your stuff isn't gone, and that the new version has just set you up with a new profile.

You can run firefox-nightly --profile ~/.mozilla/firefox/… to see which profile is right (or just check directory size :P). If you run firefox-nightly --ProfileManager, you should be able to switch the default back to the correct profile.

Hi, I lost everything on my firefox nightly: tabs, extensions, account, ... How to get them back? My version is 133.0a1. For information when I do yay, I see this: -> firefox-nightly-bin: local (133.0a1.20241012.203756-1) is newer than AUR (133.0a1.20241009.094637-1)