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.95
First Submitted: 2019-06-14 18:41 (UTC)
Last Updated: 2025-05-30 11:41 (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

« First ‹ Previous 1 .. 23 24 25 26 27 28 29 30 31 32 33 34 Next › Last »

lsf commented on 2021-04-05 20:16 (UTC)

Considering this is used to not download additional files that are not required for non-aarch64 builds, it seems like a reasonable approach to me.

FabioLolix commented on 2021-04-05 19:47 (UTC)

You are using source_aarch64=() and source_x86_64=() which are not needed since you are downloading source code not pre-compiled binaries

spoons commented on 2021-04-04 03:42 (UTC) (edited on 2021-04-06 03:17 (UTC) by spoons) 

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: More than 1 GPU detected via PCI, cannot deduce vendor (t=0.426795) [GFX1-]: More than 1 GPU detected via PCI, cannot deduce vendor
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: More than 1 GPU detected via PCI, cannot deduce vendor (t=0.426795) |[1][GFX1-]: PCI candidate 0x10de/0x1b80 (t=0.42681) [GFX1-]: PCI candidate 0x10de/0x1b80
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: More than 1 GPU detected via PCI, cannot deduce vendor (t=0.426795) |[1][GFX1-]: PCI candidate 0x10de/0x1b80 (t=0.42681) |[2][GFX1-]: PCI candidate 0x10de/0x1380 (t=0.426815) [GFX1-]: PCI candidate 0x10de/0x1380
console.warn: SearchSettings: "get: No settings file exists, new profile?" (new Error("", "(unknown module)"))

###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost

Firefox exited with code -135 during profile initialization
==> ERROR: A failure occurred in build().
    Aborting...
error making: librewolf

This package will not build on my 'dual vendor' gpu systems.

JcNils commented on 2021-04-03 21:29 (UTC)

@lsf It is weird!

It worked fine when I installed Librewolf the first time. I guess I might have messed things when I installed some other package.

My TERM is xterm-256color. I am using the default fish from Manjaro installation.

ncurses exists, reinstalling it doesn't seem to fix the terminfo database

infocmp -D returns /bin/fish

Thank you very much for pointing me in the right direction, I will investigate it further.

While writing this I realized that the first time I installed Librewolf was not from the terminal, but from the add/remove software. And the first time I tried to update there was an error, but removing the package and installing from there made it work. So I am trying that again.

Right now everything seems to be building fine.

But I still need to figure out why ncurses database doesn't work if I am using yay -S Librewolf from terminal.

lsf commented on 2021-04-03 20:10 (UTC)

@JcNils that's quite an odd error ^^

Most of the terminfo files are provided by ncurses, which is required by so many packages that I'd just assume it's installed already, so my only idea would be that you've set an "unusual" $TERM for which no appropriate terminfo is installed (or $TERM is set by your terminal emulator by something unusual) and the appropriate terminfo is not installed as well (for some terminal emulators separate packages are available, eg. kitty-terminfo, termite-terminfo etc.)

That's something I'd look into first and see where that leads you :)

JcNils commented on 2021-04-03 19:13 (UTC)

Hi, I am on Manjaro, and when I try to update or install it I get an error: could not find terminfo database.

env | grep TERM shows that the variable is there.

I wonder what is missing.

Full error:

Error running mach:

    ['build']

The error occurred in code that was called by the mach command. This is either
a bug in the called code itself or in the way that mach is calling it.
You can invoke |./mach busted| to check if this issue is already on file. If it
isn't, please use |./mach busted file build| to report it. If |./mach busted| is
misbehaving, you can also inspect the dependencies of bug 1543241.

If filing a bug, please include the full output of mach, including this error
message.

The details of the failure are as follows:

_curses.error: setupterm: could not find terminfo database

  File "/home/pc/.cache/yay/librewolf/src/firefox-87.0/python/mozbuild/mozbuild/build_commands.py", line 146, in build
    return driver.build(
  File "/home/pc/.cache/yay/librewolf/src/firefox-87.0/python/mozbuild/mozbuild/controller/building.py", line 1083, in build
    footer = BuildProgressFooter(self.log_manager.terminal, monitor)
  File "/home/pc/.cache/yay/librewolf/src/firefox-87.0/python/mozbuild/mozbuild/controller/building.py", line 651, in __init__
    Footer.__init__(self, terminal)
  File "/home/pc/.cache/yay/librewolf/src/firefox-87.0/python/mozterm/mozterm/widgets.py", line 12, in __init__
    self.term = terminal or Terminal()
  File "/home/pc/.cache/yay/librewolf/src/firefox-87.0/python/mozterm/mozterm/terminal.py", line 53, in Terminal
    return blessings.Terminal(**kwargs)
  File "/home/pc/.cache/yay/librewolf/src/firefox-87.0/third_party/python/blessings/blessings/__init__.py", line 97, in __init__
    setupterm(kind or environ.get('TERM', 'unknown'),
==> ERROR: A failure occurred in build().
    Aborting...
checking dependencies...

Packages (1) lld-11.1.0-1

0000000000 commented on 2021-03-30 19:27 (UTC)

should I just throw puter out the window?

https://imgur.com/4jcmzki

what do ty

lsf commented on 2021-03-27 00:27 (UTC) (edited on 2021-03-27 00:28 (UTC) by lsf)

np :)

btw: I've just discovered firedragon yesterday – looks great, and it's cool to see librewolf being adapted and customized! :)

dr460nf1r3 commented on 2021-03-27 00:00 (UTC)

You are totally right, it was an incorrectly cached patch. Sorry for the inconvenience.

lsf commented on 2021-03-26 18:10 (UTC)

@dr460nf1r3 can't reproduce that. If the checksums already fail, that indicates that your build system might use some cached files somewhere? (Only the unity-menubar.patch has changed (which isn't applied by default) but even that one applies cleanly for me when doing a fresh checkout of https://aur.archlinux.org/librewolf and running makepkg with the relevant line uncommented.)

Considering your logs show

Fetching origin
  -> Found megabar.patch
  -> Found remove_addons.patch
  -> Found context-menu.patch
  -> Found unity-menubar.patch
  -> Found mozilla-vpn-ad.patch

(and not downloading them) that might indeed be a possibility (as in: they're either cached somewhere or provided in a step that's not part of the logs, and something's going wrong at that point).

« First ‹ Previous 1 .. 23 24 25 26 27 28 29 30 31 32 33 34 Next › Last »