Package Details: librewolf 1:139.0.1_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: 8.08
First Submitted: 2019-06-14 18:41 (UTC)
Last Updated: 2025-05-30 11:41 (UTC)

Dependencies (62)

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

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

AndyRTR commented on 2024-08-16 15:02 (UTC)

For me adding "export LIBGL_ALWAYS_SOFTWARE=true" fixed the build in a clean chroot using the official build server.

mabod commented on 2024-08-15 08:51 (UTC) (edited on 2024-08-15 08:52 (UTC) by mabod)

I had a successfull build with 

export LIBGL_ALWAYS_SOFTWARE=true
export GALLIUM_DRIVER=softpipe
makepkg

Thanks, @xiota, for mentioning GALLIUM_DRIVER!

xiota commented on 2024-08-14 21:53 (UTC) (edited on 2024-08-14 21:53 (UTC) by xiota)

I had a successful build. Those having problems can try setting MESA_LOADER_DRIVER_OVERRIDE and/or GALLIUM_DRIVER. (I don't know valid values.) Can look for other variables to try at Mesa Environment Variables.

mabod commented on 2024-08-14 16:11 (UTC)

@lahwaacz: I have the exact same issue. LIBGL_ALWAYS_SOFTWARE=true does not help anymore.

lahwaacz commented on 2024-08-14 15:52 (UTC)

With 129.0.1 I've got this error first, building in a clean chroot:

 0:23.97 Created package: /build/librewolf/src/librewolf-129.0.1-1/obj-x86_64-pc-linux-gnu/dist/librewolf-129.0.1-1.en-US.linux-x86_64.tar.bz2
  Parallelism determined by memory: using 32 jobs for 32 cores based on 125.7 GiB RAM and estimated job size of 1.0 GiB
MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)
libEGL warning: egl: failed to create dri2 screen
[Parent 35480, Main Thread] ###!!! ABORT: file resource://gre/modules/addons/XPIProvider.sys.mjs:2653
started SP3 server on port 8000
Firefox exited with code -11 during profile initialization

I've tried uncommented LIBGL_ALWAYS_SOFTWARE=true which used to be necessary before (not for the past few versions), but the error is still almost the same:

 0:23.84 Created package: /build/librewolf/src/librewolf-129.0.1-1/obj-x86_64-pc-linux-gnu/dist/librewolf-129.0.1-1.en-US.linux-x86_64.tar.bz2
  Parallelism determined by memory: using 32 jobs for 32 cores based on 125.7 GiB RAM and estimated job size of 1.0 GiB
[Parent 35481, Main Thread] ###!!! ABORT: file resource://gre/modules/addons/XPIProvider.sys.mjs:2653
started SP3 server on port 8000
Firefox exited with code -11 during profile initialization

lsf commented on 2024-08-13 21:03 (UTC)

I'll try to get 129.0.1 out asap, and have that with a patch included for it. (upstream Arch firefox already has it: https://gitlab.archlinux.org/archlinux/packaging/packages/firefox/-/commit/f5580e563ac0dc7f0095af92bc59d849f0f45849#8e7eaa4290280247934b32ba3e259e8f94ff94d8)

mabod commented on 2024-08-13 20:34 (UTC)

I have the exact same compile error like @lahwaacz

lahwaacz commented on 2024-08-13 20:09 (UTC)

Building 129 fails:

 0:16.26 called `Result::unwrap()` on an `Err` value: "Couldn't parse config file: TOML parse error at line 363, column 1\n    |\n363 | \"Keyframe\" = \"Keyframe\"\n    | ^\nduplicate key `Keyframe` in table `export.rename`\n."

Brummbaer commented on 2024-08-03 18:48 (UTC)

@NaBoo

That worked, thank you :).

NaBoo commented on 2024-08-03 14:50 (UTC)

@Brummbaer I had the same error as you, upgrading the rust toolchain helped me

rustup update

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