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 .. 5 6 7 8 9 10 11 12 13 14 15 .. 19 Next › Last »

lsf commented on 2022-04-10 19:35 (UTC)

@ImperatorStorm: can't reproduce this on my end. Maybe it's something with your librewolf config (fonts?), or global/system font settings? You could try running librewolf with a fresh profile to see if it's caused by your config.

ImperatorStorm commented on 2022-04-10 19:31 (UTC)

librewolf 99.0 builds seem to have very broken spacing, see https://i.imgur.com/wTSrSsB.png

numbers are also rendering incorrectly, see https://i.imgur.com/FOVq2oP.png

lsf commented on 2022-04-10 09:30 (UTC)

@mekb: yeah, unfortunately the current 99.0-1 builds are partially broken – sorry about that! I'm already getting a fixed release ready (99.0-2); just waiting for the last build to finish – shouldn't be much longer.

mekb commented on 2022-04-10 09:26 (UTC)

99.0-1 has sync, shortcuts, pocket, etc. enabled, this should be disabled. next version should remove it again

<deleted-account> commented on 2022-03-20 03:31 (UTC)

Can't install LibreWolf because of a PGP key error. I've tried "gpg --keyserver..." command below but it didn't work out.

JordanPlayz158 commented on 2022-02-23 17:25 (UTC) (edited on 2022-02-23 18:09 (UTC) by JordanPlayz158)

Not sure if my mirrors haven't gotten the update yet in Manjaro or not but currently for me, GLIBC is 2.33-5 not 2.34 so be sure you have GLIBC 2.34 installed or can be upgraded to after upgrading from 95->97 otherwise you won't be able to start Librewolf after updating due to "/usr/lib/librewolf/librewolf: /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/librewolf/librewolf)"

Edit: Git commit 87af4bfa3892e73c9d9dc17756366ab05eb348bd or v97.0-1 (v97.0) still works with GLIBC 2.33-5.

lsf commented on 2022-02-21 15:35 (UTC)

Ah, yes, that seems like (…again) to be a Manjaro-mess. Basically they've added ffmpeg4.4, while not yet having updated ffmpeg to 5. And if that's been built against something not in stable, that's of course a bit, uh, odd.

Seems like in the meantime you could either edit the PKGBUILD to require ffmpeg only, as long as Manjaro still has ffmpeg <5 in stable – or you could install ffmpeg 5 and x264 from some testing/unstable/staging-repo and hope nothing else breaks? (I'd be reluctant about that ^^)

Vedro commented on 2022-02-21 15:17 (UTC)

Seems like ffmpeg4.4 has been built against the Staging repo. libx264.so=164-64 is in staging repo

Vedro commented on 2022-02-21 15:13 (UTC)

 -> Could not find all required packages:
    libx264.so=164-64 (Wanted by: librewolf-bin -> ffmpeg4.4)

system is fully updated

lsf commented on 2022-02-21 08:55 (UTC)

@pacman41: this should only happen if you haven't updated the rest of the system yet (ie. pacman -Syu)?