| Git Clone URL: | https://aur.archlinux.org/palemoon.git (read-only, click to copy) |
|---|---|
| Package Base: | palemoon |
| Description: | Open source web browser based on Firefox focusing on efficiency. |
| Upstream URL: | https://www.palemoon.org/ |
| Keywords: | browser goanna web |
| Licenses: | GPL, MPL, LGPL |
| Submitter: | artiom |
| Maintainer: | WorMzy |
| Last Packager: | WorMzy |
| Votes: | 141 |
| Popularity: | 0.017697 |
| First Submitted: | 2014-06-05 10:54 (UTC) |
| Last Updated: | 2024-05-11 23:49 (UTC) |
It is not an issue with palemoon itself, but running the plugin-container results in
# /usr/lib/palemoon/plugin-container
/usr/lib/palemoon/plugin-container: error while loading shared libraries: libxul.so: cannot open shared object file: No such file or directory
But I am not sure if there are circumstances where running this binary from command line is needed.
@haawda: what is the actual problem? libxul.so is loaded for me:
$ strace palemoon |& grep libxul
access("/usr/lib/palemoon/libxul.so", R_OK) = 0
openat(AT_FDCWD, "/usr/lib/palemoon/libxul.so", O_RDONLY) = 4
openat(AT_FDCWD, "/usr/lib/palemoon/libxul.so", O_RDONLY|O_CLOEXEC) = 4
@micwoj92: Upstream release new versions semi-regularly (sometimes multiple releases per month). Although the initial clone may be substantial, every update after that will only include the upstream changes since the last time you pulled the repos, drastically reducing the amount of bandwidth consumed in the long run.
Is there a reason why this does not download tarballs? This would greatly reduce download from 730+ to only about 200 MB.
There seem to be some issues with libraries not found. But they are there.
ldd /usr/lib/palemoon/plugin-container
libxul.so => not found
ldd /usr/lib/palemoon/libxul.so
libmozsqlite3.so => not found
liblgpllibs.so => not found
ldd /usr/lib/palemoon/libsoftokn3.so
libmozsqlite3.so => not found
ldd /usr/lib/palemoon/libmozavcodec.so
libmozavutil.so => not found
ldd /usr/lib/palemoon/browser/components/libbrowsercomps.so
libxul.so => not found
This output comes from the checkrebuild script included in the rebuild-detector package run wit -v option, but plain ldd tells the same.
As always, you need to import GPG keys manually (and ideally verify them out-of-band). Make sure gpg is set up with a keyserver, then run this:
$ gpg --recv-key 40481E7B8FCF9CEC
So just now updating four palemoons on four systems and after 2 I get:
Pale-Moon git repo ... FAILED (unknown public key 40481E7B8FCF9CEC)Pale-Moon git repo ... FAILED (unknown public key 40481E7B8FCF9CEC)
:(
Further note: Upstream have renamed the repositories again. If you previously modified your git clone configs to point to https://repo.palemoon.org/MCP/... you will need to edit them again to point to https://repo.palemoon.org/MoonchildProductions/...
Note the repositories have moved to https://repo.palemoon.org/MoonchildProductions/Pale-Moon and https://repo.palemoon.org/MoonchildProductions/UXP, if you previously cloned the repos, you can update the URL in the config files (i.e. $SRCDEST/Pale-Moon/config and $SRCDEST/UXP/config) so you don't need to clone the full repo again.
Thanks for the heads up, update pushed.
@WorMzy change source links please
Pinned Comments
WorMzy commented on 2021-03-02 16:19 (UTC) (edited on 2022-08-03 21:12 (UTC) by WorMzy)
The following key is used to sign release commits:
40481E7B8FCF9CEC
Import it into your keyring however you want.
https://wiki.archlinux.org/index.php/GnuPG#Import_a_public_key