Package Details: firefox-nightly 132.0a1+20240903.1+he8cf043939ae-1

Git Clone URL: https://aur.archlinux.org/firefox-nightly.git (read-only, click to copy)
Package Base: firefox-nightly
Description: Fast, Private & Safe Web Browser (Nightly version)
Upstream URL: https://www.mozilla.org/firefox/channel/desktop/#nightly
Keywords: browser gecko web
Licenses: MPL-2.0
Submitter: None
Maintainer: heftig
Last Packager: heftig
Votes: 611
Popularity: 1.46
First Submitted: 2008-09-10 14:23 (UTC)
Last Updated: 2024-09-03 16:13 (UTC)

Dependencies (57)

Sources (5)

Pinned Comments

heftig commented on 2022-07-27 22:26 (UTC)

Instead of building this yourself, please use the repository from https://bbs.archlinux.org/viewtopic.php?id=117157.

Not only do you skip the very time-consuming builds, but the published package also has debug symbols at Mozilla's crash reports service, which helps tremendously with finding or filing bugs for any crashes you get.

I consider this the canonical firefox-nightly package for Arch Linux.

[heftig]
SigLevel = Optional
Server = https://pkgbuild.com/~heftig/repo/$arch

Alternatively, download Firefox Nightly straight from Mozilla, extract it to a writable place (e.g. ~/.local/firefox-nightly) and let it update itself using the integrated updater.

Latest Comments

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

Archange commented on 2019-06-02 17:28 (UTC)

Known and intentional. pacaur is (or at least was) an AUR helper that knew how to handle this, just like any other -git or VCS package for instance.

leo_sk commented on 2019-06-02 15:52 (UTC)

@ArchangeGabriel:I asked because because pamac (using yaourt backend) was showing the latest version to be 69.0a1.20190521-1 for almost a week without any update. However on manually installing it again today, nightly updated to 69.0a1.20190602-1. Now my installed version is 69.0a1.20190602-1 but pamac still shows the latest version is 69.0a1.20190521-1 and that i am using outdated version. On updating however, I still get the 2nd June's build. Is this behaviour known and intentional, or is it a bug specific to me?

Archange commented on 2019-06-01 21:43 (UTC)

@leo_sk: It is updated at the frequency you update it (at most once per day). The PKGBUILD automatically download the latest tarballs from upstream. So at any given time, if you build the PKGBUILD you are at most 1 day behind (if you already tried to build on the same day, before new tarballs were uploaded upstream).

leo_sk commented on 2019-06-01 20:58 (UTC)

Just wanted to know how frequently this package is updated and how up to date is it with latest nightly?

SamWhited commented on 2019-03-26 15:11 (UTC)

FWIW, I no longer have this problem and assume that it had been fixed. Are you sure it's still happening if you try to update again?

CoolOppo commented on 2019-03-26 15:04 (UTC)

I'm having the exact same issue as @SamWhited.

SamWhited commented on 2019-03-21 14:43 (UTC) (edited on 2019-03-21 14:43 (UTC) by SamWhited)

Currently getting a bad signature.

20190321-firefox-68.0a1.en-US.linux-x86_64.tar.bz2 ... FAILED (bad signature from public key BBBEBDBB24C6F355)
==> ERROR: One or more PGP signatures could not be verified!

Archange commented on 2019-01-22 14:17 (UTC)

@mnussbaum: Have you actually tried to install this package? The PKGBUILD automatically download the latest tarball in the current branch.

nika commented on 2018-12-12 12:53 (UTC)

Does not install the latest nightly, but you can increase the version and package by editing manually and bump to 66.a01

blackout commented on 2018-11-16 10:51 (UTC) (edited on 2018-11-16 10:58 (UTC) by blackout)

https://glandium.org/blog/?p=3899

I got following error and it hung fter the libegl message

$ GDK_BACKEND=wayland firefox-nightly

(firefox:30634): Gtk-WARNING **: 11:44:10.658: Theme parsing error: <data>:1:34: Expected ')' in color definition

(firefox:30634): Gtk-WARNING **: 11:44:10.658: Theme parsing error: <data>:1:77: Expected ')' in color definition Attempting load of libEGL.so ^C

but when started normally with xwayland and closing after and tried again it worked. whatever Firefox wayland works :)