| 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: | 644 |
| Popularity: | 19.83 |
| First Submitted: | 2019-06-16 13:12 (UTC) |
| Last Updated: | 2026-07-15 08:05 (UTC) |
On installation of any 149 build I'm getting:
File "/usr/lib/librewolf/gmp-clearkey/0.1/libclearkey.so" from package "librewolf-bin" is missing dependency "libmozsqlite3.so"
Seems to also be an issue on Floorp (another Firefox based browser): https://aur.archlinux.org/packages/floorp-bin#comment-1063422
So it might be upstream of LibreWolf.
@Squidward Yes, there they are. Thanks for that. I just tried to find them my usual way be using the search bar at the top of the settings page. Not sure why they didn't show up, but at least now I know they're under that section of settings.
@jolliness9796 i seem to still have thoose options on "librewolf" section of the settings. although i already have a firefox profile with plugins + other stuff so its not a fresh install. and they seem to enable/disable just fine
The latest build seems to be missing sync, and resist fingerprinting options (enable / disable) in the settings. Maybe more, but those are the two that I immediately noticed upon a fresh install this morning.
==> Checking source files with sha256sums...
source ... Critical: Invalid object name: 149.0.2-1
default192x192.png ... Success
librewolf.desktop ... Success
==> ERROR: One or more files failed validation!
Error: Sources for ‘librewolf-bin-1:149.0.2_1-1’ could not be downloaded:
Error: Packages could not be built: librewolf-bin-1:149.0.2_1-1
@lsf , have you considered licensing the PKGBUILD under the 0BSD license? The package will become eligible for moving into the official repos.
the
>> Remember to check for changes in /usr/lib/librewolf/librewolf.cfg.pacnew
>> as those will not automatically overwrite your existing librewolf.cfg.
>>
>> We would encourage you to migrate your own changes to the new overrides file
>> at ~/.librewolf/librewolf.overrides.cfg instead, so making changes directly
>> in your librewolf.cfg is not necessary anymore (in most cases at least).
>>
>> Check out https://gitlab.com/librewolf-community/settings/-/merge_requests/13
>> for more information on this.
Section still points to a gitlab when everything for librewolf has moved to codeberg... please update the PKGBUILD
Thank you everyone for your replies, I just happened to see @pazyko's email first and that worked for me.
@ pazyko..."Using yay you can fix it by doing a clean build (yay -Su librewolf-bin --answerclean all)"
This worked for me, thx!
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.