Pale Moon (slarm64 , aarch64)
|
I have a few issues with palemoon here.
I'll grab chromium next time and try that, as it has the chrome engine. EDIT: On the site above, Chrome takes about 7 seconds. FF does it in about 10 seconds, IIRC. |
|
Thanks, but that's compiled against glibc-2.34, which I presume is ~current. I'm on 15.0 which has glibc-2.33. Do you have the source online? I know palemoon.org does, but I presume there's a patch or three required for Aarch64.
|
yes, collected for current. build script.
|
Updated to palemoon-32.2.0, which they are claiming great things for (as usual). I used the GTK-2.x, and the changelog included this line
Code:
Fixed a build issue when building for Linux on ARM64 on later distros. |
|
I tried to get this last evening and the download kept failing at about 37 megs. Is the link good?
|
Quote:
|
Hmmph! That's giving me a 502 - bad gateway. I'll keep trying.
EDIT: I got palemoon from slarm64.org. I couldn't establish an SSL connection with wget. I tried without the 's' in https://, but that returned the same error :confused:. There must be strange things happening with my connection, or the ether at large. It used always be the case in very wet weather, but the pervasiveness of glass optical fibre here seems to have reduced that. |
I have Palemoon installed but it pukes with screenfuls of this
Code:
(pale moon:3776): Gtk-WARNING **: 18:58:33.187: Unable to locate theme engine in module_path: "murrine", Code:
! Your Pale Moon profile cannot be loaded or it may be inaccessible Personally I don't believe it. It doesn't have my profile first time out anyhow. When I saw that, I deleted anything palemoon ~/.local/share & ~/.cache but I kept the ~/.config stuff. |
|
Quote:
Code:
This file can't be downloaded securely. As for PM-32.3.0 that throws the same error exactly and doesn't run. Code:
! Your Pale Moon profile cannot be loaded or it may be inaccessible |
Well, I have Palemoon-32.3.0 working!
My SSD has the RazPi-4 image (kernel-6.4.8). At the same time I mirrored the slarm64-current and ran upgradepkg on the relevant directories. But the kernel there was 6.1.27:eek: I burned another sdcard with the image, enlarged the sdcard's ext4 partition, and copied the palemoon package into /home. I then booted on that, installed palemoon, and palemoon worked. I'm back on my ssd, now. But it seems something is off on my SSD install. Either Current had different versions up, or else it's because I lacked a clean install. I hate installation gremlins. So my next move unless you advise otherwise is to boot from the SSD, and run 'rsync -avc' to transfer everything relevant from the sdcard / to the SSD /. That will be a slow process so I'll start it tomorrow morning and let it have the day at it. It's not a fast sdcard, but who cares? I'll transfer the $PATH & LD_LIBRARY_PATH, and everything in /etc/X11 and /usr/X11R6. I will go to lengths to avoid upsetting all the careful configuration in /etc, largely because I've forgotten what I did. I have it backed up, but I have forgotten. |
Quote:
Code:
ldd /usr/lib64/palemoon-32.3.0/libxul.so |
All times are GMT -5. The time now is 10:36 PM. |