Package Details: librewolf 1:139.0.0_1-1

Git Clone URL: https://aur.archlinux.org/librewolf.git (read-only, click to copy)
Package Base: librewolf
Description: Community-maintained fork of Firefox, focused on privacy, security and freedom.
Upstream URL: https://librewolf.net/
Keywords: browser web
Licenses: MPL-2.0
Submitter: lsf
Maintainer: lsf
Last Packager: lsf
Votes: 175
Popularity: 9.51
First Submitted: 2019-06-14 18:41 (UTC)
Last Updated: 2025-05-28 17:50 (UTC)

Sources (3)

Pinned Comments

lsf commented on 2025-01-01 21:28 (UTC)

Please refrain from abusing the flagging of a package as out of date for build issues. This is not what it is supposed to be used for.

I automatically get notified of comments to this package. I do not need to be notified of whatever build problems occur (whether they are an individual's problems or the actual package's problems) twice, and not via flagging it out of date.

Issues with this package can also be reported at https://codeberg.org/librewolf/issues/issues (as it is also maintained there, at https://codeberg.org/librewolf/arch, too).

Latest Comments

1 2 3 4 5 6 .. 34 Next › Last »

marbens commented on 2025-05-22 02:52 (UTC)

@AvidSeeker how much RAM do you have? I've had problems with RAM running out while building this. oomkiller might be killing the terminal, causing SIGHUP.

xiota commented on 2025-05-22 02:50 (UTC)

@AvidSeeker yay ≠ clean chroot. Here's an alternate PKGBUILD you can try. If you have the same error, there's a problem with your system. If it succeeds, there's a problem with the AUR version.

AvidSeeker commented on 2025-05-22 02:44 (UTC)

@xiota

Yes. Even with rm -rf ~/.cache/yay/librewolf.

Problem persists even after full system upgrade. That interrupt signal even closes the shell session. I had to log yay output into a file to catch this interrupt.

xiota commented on 2025-05-19 18:22 (UTC)

@AvidSeeker Have you tried building in a clean chroot?

AvidSeeker commented on 2025-05-19 18:04 (UTC)

I keep getting a HUP signal caught

21:23.87 warning: unexpected `cfg` condition value: `testlib`
21:23.87    --> security/manager/ssl/trust_anchors/build.rs:351:11
21:23.87     |
21:23.87 351 |     #[cfg(feature = "testlib")]
21:23.87     |           ^^^^^^^^^^^^^^^^^^^ help: remove the condition
21:23.87     |
21:23.88     = note: no expected values for `feature`
21:23.88     = help: consider adding `testlib` `
...
21:44.79    Compiling topological-sort v0.1.0
21:44.98    Compiling time-macros v0.2.18
21:45.02    Compiling dns-parser v0.8.0
21:58.37    Compiling suggest v0.1.0 (https://github.com/mozilla/application-services?rev=d773da92641d92930b7308300e9fc2746a05ce6a#d773da92)
Terminated

==> ERROR: HUP signal caught. Exiting...
==> Cleaning up...

boxwood commented on 2025-04-16 21:46 (UTC) (edited on 2025-04-16 21:47 (UTC) by boxwood)

So I keep getting this build fail:

39:18.83 error: could not compile `gkrust` (lib)
39:18.85 Caused by:
39:18.91   process didn't exit successfully: `/usr/bin/rustc --crate-name gkrust [...]

GI_Jack commented on 2025-04-01 04:28 (UTC)

@xiota

Its with xvfb

xiota commented on 2025-03-17 01:27 (UTC)

@GI_Jack That is probably the profiling stage. Are you using xvfb or xwayland-run? Try the other to see if there is any difference. If not, and it bothers you enough, disable PGO.

GI_Jack commented on 2025-03-17 00:26 (UTC)

when compiling this package, librewolf is opened with test pages. This shouldn't happen for a compile job. I am not sure why its doing this, but it needs to stop

xiota commented on 2025-03-15 20:23 (UTC) (edited on 2025-03-28 01:02 (UTC) by xiota)

For those who don't want to use aur/xwayland-run-git:

_build_profiled_xvfb=true makepkg -srCf

1 2 3 4 5 6 .. 34 Next › Last »