Package Details: firefox-nightly 132.0a1+20240927.1+h79ef00c1355d-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: 610
Popularity: 0.54
First Submitted: 2008-09-10 14:23 (UTC)
Last Updated: 2024-09-27 20:33 (UTC)

Dependencies (57)

Required by (97)

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 .. 4 5 6 7 8 9 10 11 12 13 14 .. 56 Next › Last »

hsantanna commented on 2021-05-14 20:55 (UTC)

There is any procedure I should do to debug firefox-nightly with this aur package?

I just installed aur/xulrunner, but I would like to know if there is any flags that should be enabled from aur/firefox-nightly PKGBUILD to enable debug symbols, so it can be traced with gdm.

I would like to produce some stack trace when needed to report Firefox bugs.

hsantanna commented on 2021-05-14 20:37 (UTC)

@Akrai here is the Mozilla bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1711266

I will add more details there soon

Anyway, I did opened a KDE bug also, and they said it was fixed on git already and the fix will be available on KDE Plasma 5.22.0: https://bugs.kde.org/show_bug.cgi?id=437115

I'm building KDE Plasma from git right now to test it and see if the crash is solved.

akrai commented on 2021-05-14 16:16 (UTC)

Thanks hsantanna! Please open a bug report on mozilla's bugtracker

hsantanna commented on 2021-05-14 16:14 (UTC) (edited on 2021-05-14 16:42 (UTC) by hsantanna)

Updated today (2021-05-14) to 90.0a1 (2021-05-13) and I'm getting compositor crash on KDE Plasma Wayland (kwin_wayland) every time firefox-nightly is started.

So I figured out that it was related to gfx.webrender.compositor.force-enabled=true about:config setting.

Opening firefox-nightly on XWayland and setting gfx.webrender.compositor.force-enabled=false solved the compositor crashing, so I can start the current nightly version as an Wayland client again.

I'm commenting it here just in case someone get to this problem.

Archange commented on 2021-05-14 11:05 (UTC)

@xuiqzy No, I thought about it of course, but that’s not possible in an acceptable way. The thing is we only know after downloading the file, at which point the renaming already happened.

So it would require downloading the file in a variable, i.e. as part of parsing the PKGBUILD. This was pointed as a very bad practice when I did so years ago for grabbing checksums when Mozilla wasn’t signing the tarball but only the checksums file.

xuiqzy commented on 2021-05-14 10:12 (UTC)

@Archange Great with the detailed pkgver! Could you also include this info in the filename so makepkg etc don't see the version from the same day as the same (cached) version but download the new one if it has a different version? Currently same day updates require that the downloaded old sources from the same day are not present in the build directory.

Archange commented on 2021-05-14 06:50 (UTC)

@ToadKing: I’ve tweaked the pkgver to be more descriptive now. As you suggested I’m now using the full build timestamp and also the mercurial revision (as in heftig package).

ToadKing commented on 2021-03-28 03:41 (UTC)

Is it possible to use the full 14 digit timestamp from the text file on the CDN server as the version number instead of just the year/month/day part? Nightly updates can often come twice in a day and having the exact version number for those might be helpful.

nrayamjhee commented on 2021-02-26 21:51 (UTC)

@SimPilotAdamT Just change the _version = 88.0a1 and pkgver = 88.0a1.20210226 in PKGBUILD and rebuild the package for now. @Archange is probably going to update that and .SRCINFO sometime soon. Just did that so that I can get the update with doge firefox logo :D

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 56 Next › Last »