Package Details: librewolf-bin 1:139.0.0_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: 489
Popularity: 27.01
First Submitted: 2019-06-16 13:12 (UTC)
Last Updated: 2025-05-28 17:50 (UTC)

Dependencies (39)

Required by (34)

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 .. 9 10 11 12 13 14 15 16 17 18 19 .. 22 Next › Last »

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)?

pacman41 commented on 2022-02-21 01:57 (UTC)

Error on install

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

SpidFightFR commented on 2022-01-26 19:09 (UTC)

Works really great, i actually prefer librewolf over the regular firefox. (+1 upvote)

sucklessengai commented on 2022-01-01 23:48 (UTC) (edited on 2022-01-02 00:54 (UTC) by sucklessengai)

Librewolf is not opening I'm at manjaro gnome zsh: segmentation fault (core dumped) librewolf

gameslayer commented on 2022-01-01 11:32 (UTC) (edited on 2022-01-01 11:33 (UTC) by gameslayer)

Also getting a segmentation fault (core dumped) LibreWolf when I try and launch LibreWolf, might make a git issue report about it.

jost21 commented on 2021-12-30 12:47 (UTC)

I get this error segmentation fault (core dumped) LibreWolf when starting librewolf since this week

lsf commented on 2021-12-15 19:34 (UTC)

@inetbowser: thanks for chiming in with me being so slow to update things this time around!

I'll try to get things done a bit quicker next time :)

inetbowser commented on 2021-12-15 18:58 (UTC) (edited on 2021-12-15 19:05 (UTC) by inetbowser)

For anyone wondering how to manually update LibreWolf:

First clone the librewolf-bin AUR repo with

git clone https://aur.archlinux.org/librewolf-bin.git

Then create a file called pkgbuild_update.patch inside the git repo with contents:

6,7c6,7
< pkgver=94.0.2
< pkgrel=2
---
> pkgver=95.0
> pkgrel=1
33c33
< sha256sums_x86_64=('1c157969f8296b5f762c2e97a8234e770a535f1e2386fd7364f38e0369adc321'
---
> sha256sums_x86_64=('a31609ebfb3a3df7e5929e1d6ab448359f812d6f6a29c1cf6a7aee413c6eb8f1'
35c35
< sha256sums_aarch64=('0e8f4038848eac9091ae287f668c5e99a72f6d9f4dc2be4ca846e36690b51e22'
---
> sha256sums_aarch64=('3f0d7e9943f6562fa61e7326e6eb6c4e4313269477eb3350b1a241818dce4455'

Finally, navigate into the repo with a terminal, apply the patch and then run makepkg to build and install the LibreWolf 95.0:

patch PKGBUILD pkgbuild_update.patch
makepkg -si

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 :)

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 18 19 .. 22 Next › Last »