Package Details: librewolf-bin 1:150.0.3_1-1

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)

Required by (39)

Sources (7)

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 662E3CDD6FE329002D0CA5BB40339DD82B12EF16 should 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.xz tarballs 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) via gpg --refresh-keys 662E3CDD6FE329002D0CA5BB40339DD82B12EF16.

Latest Comments

« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 Next › Last »

<deleted-account> commented on 2021-06-25 11:25 (UTC)

@lsf it seemed that the default gpg --search can't identify the key:

gpg --search-keys 2954CC8585E27A3F                  
gpg: data source: https://keys.openpgp.org:443
(1)       256 bit EDDSA key D2845E1305D6E801, created: 2020-03-14
Keys 1-1 of 1 for "2954CC8585E27A3F".  Enter number(s), N)ext, or Q)uit > 1
gpg: key D2845E1305D6E801: no user ID
gpg: Total number processed: 1

However, I successfully install librewolf after using gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys 2954CC8585E27A3F Thank you very much. :)

lsf commented on 2021-06-25 08:17 (UTC)

Did gpg give you any kind of error?

I've seen issues with key servers every now and then, so maybe it hadn't properly downloaded the key?

If you want to force it to use a specific key server, you could try gpg --keyserver hkp://keyserver.ubuntu.com --search-keys 2954CC8585E27A3F, for example (or gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys 2954CC8585E27A3F).

With gpg --list-keys 2954CC8585E27A3F, you could also verify if it has actually been imported.

<deleted-account> commented on 2021-06-25 06:28 (UTC)

Hi, I used paru and manually(makepkg -ci) to install librewolf-bin but I got the same result and couldn't install it

==> Verifying source file signatures with gpg... librewolf-89.0.2-1-x86_64.pkg.tar.zst ... FAILED (unknown public key 2954CC8585E27A3F) ==> ERROR: One or more PGP signatures could not be verified! error: failed to download sources for 'librewolf-bin-89.0.2-1': :: Packages failed to build: librewolf-bin-89.0.2-1

after gpg --search-keys 2954CC8585E27A3F and paru -S --pgpfetch librewolf-bin

Thank you

maderios commented on 2021-06-04 19:57 (UTC)

@iordendev Since 2021 april, Arch install is easier with the new installer, 'archinstall'
https://wiki.archlinux.org/title/Archinstall

iordendev commented on 2021-06-04 19:49 (UTC)

@madeiros Sorry, I didn't know. I thought it was an important piece of info but wasn't directly related.

@lsf Thank you sir

lsf commented on 2021-06-04 16:38 (UTC)

Even though @maderios is not wrong, I'll still try to help: Basically it's because Manjaro is still on gcc/gcc-libs 10, while Arch (and thus, the build environment) is on 11.

gcc 11 is already in stable-staging on Manjaro, though – so it should be in stable soon, I'd assume.

Until then, you could probably either temporarily switch your Manjaro to use the stable-staging repos (which should be "stable enough") – or build LibreWolf from source to have a version that's linked against your gcc-libs.

maderios commented on 2021-06-04 16:26 (UTC)

https://bbs.archlinux.org/viewtopic.php?id=130309
These boards are for the support of Arch Linux, and Arch ONLY
If you have installed Archbang, Antergos, Chakra, Evo/Lution, Manjaro, Whatever, you are NOT running Arch Linux.

iordendev commented on 2021-06-04 15:38 (UTC) (edited on 2021-06-04 15:42 (UTC) by iordendev)

Latest version shows this error on Manjaro:

/usr/lib/librewolf/librewolf: /usr/lib/libstdc++.so.6: version 'GLIBCXX_3.4.29' not found (required by /usr/lib/librewolf/librewolf)

lsf commented on 2021-05-20 12:01 (UTC)

You have to import the maintainer's keys (once). Either manually (eg. with gpg --search-keys 2954CC8585E27A3F) or automatically (paru -S --pgpfetch librewolf-bin should do the trick).

vglinden commented on 2021-05-20 11:50 (UTC)

Hi,

I'm using paru and i'm getting this failure:

==> Verifying source file signatures with gpg...
    librewolf-88.0.1-1-x86_64.pkg.tar.zst ... FAILED (unknown public key 2954CC8585E27A3F)
==> ERROR: One or more PGP signatures could not be verified!
:: Packages failed to build: librewolf-bin-88.0.1-1

Thank you!

« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 Next › Last »