Package Details: librewolf-bin 133.0.3-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-community.gitlab.io/
Keywords: browser web
Licenses: GPL, MPL, LGPL
Conflicts: librewolf
Provides: librewolf
Submitter: lsf
Maintainer: lsf
Last Packager: lsf
Votes: 407
Popularity: 10.84
First Submitted: 2019-06-16 13:12 (UTC)
Last Updated: 2024-12-15 09:43 (UTC)

Dependencies (16)

Required by (28)

Sources (7)

Pinned Comments

lsf commented on 2021-11-10 12:14 (UTC) (edited on 2023-04-17 07:18 (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 :)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 19 Next › Last »

petris commented on 2023-10-31 14:17 (UTC)

I just wanted to note that it appears you're using the pkgrel field to indicate part of an upstream version number, however that's not what the pkgrel field is for. Per the PKGBUILD wiki:

The release number. This is usually a positive integer number that allows to differentiate between consecutive builds of the same version of a package. As fixes and additional features are added to the PKGBUILD that influence the resulting package, the pkgrel should be incremented by 1. When a new version of the software is released, this value must be reset to 1. In exceptional cases other formats can be found in use, such as major.minor.

Thus this should generally be 1 unless you need to rebuild a specific version for some reason, such as a change or fix in the PKGBUILD, bumping for dependent library versions like python, etc.

I know that the librewolf project is using -X to indicate some minor version, and that you can't use a dash in the actual package version, however you could always change this to something like 119.0.7 or 119.0r7 or similar. Note that according to vercmp, version XX > XXrX (119.0 is greater than 119.0r2 for instance), so if you go with the r version you'll want to wait until the next major release, otherwise the dot notation would work.

ron2138 commented on 2023-08-11 11:13 (UTC) (edited on 2023-08-11 11:14 (UTC) by ron2138)

With 116.0.2-1, and probably with earlier versions too, I get kernel: memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL, pid=538 'librewolf'. Can I assume it is already reported in the appropriate places, or should I report that? If so, where to? Isn't it a Firefox source code issue? The kernel message was already discussed a lot. For example, at Kernel.org Bugzilla, lkml, and lxc issue.

eNV25 commented on 2023-08-09 12:51 (UTC) (edited on 2023-08-09 12:51 (UTC) by eNV25)

To fix icon issues in KDE Plasma Wayland, add the following symlink. The desktop file name needs to match the app-id Wayland property.

ln -srvf "$pkgdir/usr/share/applications/librewolf.desktop" "$pkgdir/usr/share/applications/LibreWolf.desktop"

IpswichTriptych commented on 2023-08-03 00:58 (UTC) (edited on 2023-08-10 20:52 (UTC) by IpswichTriptych)

rebuild-detector is complaining about librewolf-bin as of 2023-08-02. The reason is:

ldd /usr/lib/librewolf/gmp-clearkey/0.1/libclearkey.so
    libmozsqlite3.so => not found

yakoi commented on 2023-07-26 14:55 (UTC)

Hi, I installed librewolf-bin and the resulting /usr/lib/librewolf/librewolf.cfg file does not contain the defaultPref to load the librewolf.overrides.cfg file. I checked in the sources of the librewolf package and this is what I found and copied into my librewolf.cfg file to make the overrides work :

/** [CATEGORY] OVERRIDES
 * allow settings to be overriden with a file placed in the right location
 * https://librewolf.net/docs/settings/#where-do-i-find-my-librewolfoverridescfg
 */
let profile_directory;
if (profile_directory = getenv('USERPROFILE') || getenv('HOME')) {
  defaultPref('autoadmin.global_config_url', `file://${profile_directory}/.librewolf/librewolf.overrides.cfg`);
}

This should be included in the default librewolf.cfg file that comes with package librewolf-bin.

Thanks.

heapifyman commented on 2023-06-19 22:00 (UTC)

It appears that the latest version 114.0.1-2 broke support for FIDO2 / webauthn?

There's an upstream issue in firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1836722

As a workaround one can set security.webauthn.ctap2 to false in about:config.

A fix seems to be planned for firefox 116

heapifyman commented on 2023-06-12 10:48 (UTC) (edited on 2023-06-12 10:49 (UTC) by heapifyman)

It appears that the latest version 114.0.1-2 broke support for FIDO2 / webauthn?

All my FIDO2 USB tokens used as 2nd factor are failing on multiple pages (gitlab, nextcloud, etc.). The same tokens work fine when used in Brave browser.

Is there any new setting that needs to be adjusted to re-enable FIDO2 / webauthn support?

heapifyman commented on 2023-05-02 08:32 (UTC)

I am getting

ERROR: Integrity checks (sha256) differ in size from the source array.

when trying to update to version 112.0.2-1.

It seems that there is a 'SKIP' missing in both sha256sums_x86_64 and sha256sums_aarch64?

Connabl commented on 2023-04-20 22:54 (UTC) (edited on 2023-04-20 22:55 (UTC) by Connabl)

The file in question for @Spitap's fix below is: /home/yourusername/.local/share/applications/librewolf.desktop

Thanks @Spitap!

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 19 Next › Last »