@FShip You should be able to manually download the GPG key from:
Then import it with:
gpg --import librewolf.asc
| Git Clone URL: | https://aur.archlinux.org/librewolf-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | librewolf-bin |
| Description: | Community-maintained fork of Firefox, focused on privacy, security and freedom. |
| Upstream URL: | https://librewolf.net/ |
| Keywords: | browser web |
| Licenses: | MPL-2.0 |
| Conflicts: | librewolf |
| Provides: | librewolf |
| Submitter: | lsf |
| Maintainer: | lsf |
| Last Packager: | lsf |
| Votes: | 626 |
| Popularity: | 24.26 |
| First Submitted: | 2019-06-16 13:12 (UTC) |
| Last Updated: | 2026-05-13 07:44 (UTC) |
« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 29 Next › Last »
@FShip You should be able to manually download the GPG key from:
Then import it with:
gpg --import librewolf.asc
Nothing I tried with the keys works: pacman-key --recv-keys has no effect, gpg --keyserver crashes with
gpg: error writing keyring '[keyboxd]': SQL library used incorrectly
gpg: error reading '[stream]': SQL library used incorrectly
So how do I install the browser?
So what is the necessary update to the librewolf install docs to get this working? If the instructions on the main website are insufficient, as clearly indicated here, that needs to be addressed. Key server issues in the year/month of our lord Feb 2025?
You shouldn't use pkgrel for the upstream version, but instead use an underscore in pkgver.
Sources:
https://wiki.archlinux.org/title/PKGBUILD#pkgver
Also, here's a patch that you can apply with git am <filename>, that fixes this problem: https://pastebin.com/3jEcpFvd
Edit: I've also made this as a PR on Codeberg.
"Getting SIGNATURE NOT FOUND"
Installing with 'yay' works on my machine (Big Linux)...
$ yay -S librewolf-bin ........... " :: (1/1) Parsing SRCINFO: librewolf-bin gpg: error reading key: No public key :: PGP keys need importing: -> 662E3CDD6FE329002D0CA5BB40339DD82B12EF16, required by: librewolf-bin :: Import? [Y/n] y :: Importing keys with gpg... gpg: key 40339DD82B12EF16: public key "LibreWolf Maintainers gpg@librewolf.net" imported gpg: Total number processed: 1"
Getting SIGNATURE NOT FOUND, none of the key-installation hints from the comments here seem to resolve that issue (Manjaro KDE Plasma, on 6.12.11-1)
gpg imported the missing key 8A74EAAF89C17944 and stated the source is: https://185.125.188.27:443
Going there with the browser, I got the message, it's not safe (not https).
I think KDE Wayland wants the .desktop file to be named LibreWolf.desktop instead of librewolf.desktop, the alt tab menu shows Librewolf without an icon unless I copy the .desktop file from /usr/share/applications/ into ~/.local/share/applications and name it LibreWolf.desktop.
Will this ever adopted by arch main repos ?
Specifying the port # while importing the keys helped me:
gpg --keyserver hkps://keyserver.ubuntu.com:443 --search-keys 662E3CDD6FE329002D0CA5BB40339DD82B12EF16
Pinned Comments
lsf commented on 2021-11-10 12:14 (UTC) (edited on 2026-05-07 09:38 (UTC) by lsf)
https://wiki.archlinux.org/title/Arch_User_Repository#Acquire_a_PGP_public_key_if_needed
gpg --keyserver hkp://keyserver.ubuntu.com --search-keys 031F7104E932F7BD7416E7F6D2845E1305D6E801/edit: starting with 112.0-1, the binaries are signed with the maintainers shared key, so
gpg --keyserver hkp://keyserver.ubuntu.com --search-keys 662E3CDD6FE329002D0CA5BB40339DD82B12EF16should do the trick instead. I've also signed the key with the previously used key, so you have at least some guarantee that it's not a malicious attack :)/edit: (2026-05-07): The upstream signing sub-key was rotated, and the
.tar.xztarballs will now be signed with a new subkey. The main key id (0x662E3CDD6FE329002D0CA5BB40339DD82B12EF16) remains unchanged though, so should you get an error during signature verification about a missing (sub)key, all that's required would be to refresh the key(s) viagpg --refresh-keys 662E3CDD6FE329002D0CA5BB40339DD82B12EF16.