Pale Moon x86-64 SSE2/AVX2

[ron_1]

I think I had the old one imported. But when I try to import the new one, it doesn't seem to take it. Am I supposed to purge the old one, then import the new one? How do I do that?

[Veit Kannegieser]

Off-topic:

Code: Select all

gpg: key 865E6C87C65285EC: no public key for trusted key - skipped

you could download and install the key for Travis from the download page - https://www.palemoon.org/0xC65285EC.asc directly,
or comment out the trusted-key 439F46F42C6AE3D23CF52E70865E6C87C65285EC line from you gnupg user profiles gpg.conf.
Please see some pages before

[ron_1]

Off-topic:

you could download and install the key for Travis from the download page

Thanks for the tip.

[Nuck-TH]

34.1 builds are now available.

[karlchen]

Thank you very much, Moonchild and Nuck-TH.

Code: Select all

$ inxi -SCx3; palemoon --version
System:    Host: voyager Kernel: 5.15.0-171-generic arch: x86_64 bits: 64 compiler: gcc v: 11.4.0 clocksource: tsc
           Desktop: Cinnamon v: 6.0.4 tk: GTK v: 3.24.33 wm: Muffin v: 6.0.1 vt: 7 dm: LightDM v: 1.30.0 Distro: Linux Mint
             21.3 Virginia base: Ubuntu 22.04 jammy
CPU:       Info: quad core model: Intel Core2 Quad bits: 64 type: MCP smt: <unsupported> arch: Core2 Merom rev: 7 cache:
             L1: 256 KiB L2: 8 MiB
           Speed (MHz): avg: 1595 min/max: 1600/2400 cores: 1: 1595 2: 1595 3: 1595 4: 1595 bogomips: 19140
           Flags-basic: ht lm nx pae sse sse2 sse3 ssse3 vmx
           
Moonchild Productions Pale Moon 34.1.0

[back2themoon]

Hello, Nuck-TH,

Perhaps you've already been notified somehow, but there's talk in this topic about a potential issue with your builds.

[Nuck-TH]

34.2 builds are uploaded

as i said in that topic, i don't know what can cause issues, so no modifications to the build process is made.

[flamelord]

Does this fix cloudflare? Or should I wait for the automatic update to roll out?
I can't remember which of these builds is for my machine.

[back2themoon]

It won't fix Cloudflare. Only CF know what they changed, and it's up to them to fix it and let everyone else know what happened. Also, there is no mention of this problem in Pale Moon's 34.2.0 release notes. There is a Cloudflare entry, but it's about something else.

Wait for the automatic update or find out yourself in about:buildconfig. Look for "AVX2" in there. If you don't have it, you are on the SSE2 build and should have "target=x86_64".

[back2themoon]

By the way, something seems off with the update check? I only get a blank Software Update window.

[flamelord]

It won't fix Cloudflare. Only CF know what they changed, and it's up to them to fix it and let everyone else know what happened. Also, there is no mention of this problem in Pale Moon's 34.2.0 release notes. There is a Cloudflare entry, but it's about something else.

Wait for the automatic update or find out yourself in about:buildconfig. Look for "AVX2" in there. If you don't have it, you are on the SSE2 build and should have "target=x86_64".

Yeah

target
x86_64-pc-mingw32

I'll just wait for Moonchild to roll the update though since I just like updating directly from the browser

[nicolaasjan]

By the way, something seems off with the update check? I only get a blank Software Update window.

Same here.
I had to update manually.

Also still crashes with the 34.2.0 AVX2 build on a GitHub page.

[back2themoon]

Also still crashes with the 34.2.0 AVX2 build on a GitHub page.

The mainline AVX build does not?

[flamelord]

By the way, something seems off with the update check? I only get a blank Software Update window.

Same here.
I had to update manually.

Also still crashes with the 34.2.0 AVX2 build on a GitHub page.

Isn't that just because Moonchild still hasn't rolled out the update for the 3rd party builds?

[back2themoon]

These builds are already available for download. Installing them manually or via auto-update does not make any difference.

Also, I think it's Nuck-TH that "rolls out the automatic updates" for these builds. They are first available as manual downloads, and later pushed to the auto-updating channel.

[flamelord]

These builds are already available for download. Installing them manually or via auto-update does not make any difference.

Also, I think it's Nuck-TH that "rolls out the automatic updates" for these builds. They are first available as manual downloads, and later pushed to the auto-updating channel.

Good to know
Whatever the case, maybe they're testing it a bit more on those problems before they roll the auto-update/Help menu
There has been a time or two when I had to wait a bit for the update to get rolled out automatically, I don't think it's a bug with the software update window

[UCyborg]

Also still crashes with the 34.2.0 AVX2 build on a GitHub page.

The mainline AVX build does not?

Seems random to me, the previous Nuck-TH's 34.1.0 SSE2 build did, my self-built 34.2.0 AVX (1) build seems to as well. I've had half the RAM free during build, freshly booted Windows 10 1809 today on bare hardware (not virtual machine), February 2026 update to Visual Studio 2026 using 14.44.35207 version of build tools.

[Nuck-TH]

Also, I think it's Nuck-TH that "rolls out the automatic updates" for these builds. They are first available as manual downloads, and later pushed to the auto-updating channel.

No, it isn't. I haven't access to infra, so actually rolling out autoupdate isn't up to me, i just put mar(update) arcives in non-public dir in same ftp as arcives/installers.

[Moonchild]

I apologise for the delay getting the automatic updates to production.

[flamelord]

I apologise for the delay getting the automatic updates to production.

Just to confirm: The updates haven't been rolled out yet, right?
I'm getting a blank software update window.