Package Details: palemoon 1:33.1.0-1

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.023531
First Submitted: 2014-06-05 10:54 (UTC)
Last Updated: 2024-04-23 22:42 (UTC)

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

Latest Comments

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

micwoj92 commented on 2021-02-04 22:25 (UTC)

@jghodd that commit should be included

https://repo.palemoon.org/MoonchildProductions/Pale-Moon/commit/79ff7796e598775f30e00ec251e5c094e31ebe94

jghodd commented on 2021-02-04 22:11 (UTC)

Getting a build error in Pale-Moon/platform/dom/html/HTMLMenuItemElement.cpp

Here's the bug report which has been closed and fixed. PKGBUILD needs to be updated to a more recent commit to include this fix.

https://repo.palemoon.org/MoonchildProductions/UXP/issues/1723

micwoj92 commented on 2021-02-02 22:33 (UTC)

Thanks, I've made it. Just copypaste, but replaced gtk2 with gtk3, AFAIK it still needs gtk2 to build but I am not sure if it's needed to run.

https://aur.archlinux.org/packages/palemoon-gtk3/

WorMzy commented on 2021-02-02 21:55 (UTC)

I have no interest in building palemoon with gtk3. Feel free to make a palemoon-gtk3 package though.

micwoj92 commented on 2021-02-02 19:46 (UTC)

So now that the official releases provide both gtk2 and gtk3 could this package use gtk3 and new palemoon-gtk2 be made? or maybe otherwise, this stays gtk2 and there is palemoon-gtk3?

haawda commented on 2020-12-22 16:26 (UTC)

WorMzy, I found that palemoon-bin has exactly the same behaviour, and it indeed seems a feature, not a bug. And it is old...

See https://forum.palemoon.org/viewtopic.php?t=11800

WorMzy commented on 2020-12-22 15:29 (UTC)

@haawda: I don't think plugin-container should be called by itself. It's called by the browser as required which presumably handles shared library access.

See https://support.mozilla.org/en-US/kb/what-is-plugin-container for Firefox's description of plugin-container (I couldn't find an equivalent page on the palemoon site, but I doubt the functionality is that different)

@micwoj92: Feel free to do so locally, but I suspect duplicate packages that just uses a different source to the original would be removed from the AUR by TUs. Feel free to ask on the mailing list (aur-general) and/or IRC (#archlinux-aur on freenode) if you want to confirm.

Alternatively, maybe use palemoon-bin?

micwoj92 commented on 2020-12-21 18:56 (UTC)

That makes sense. I hope I am not the only one frequently deleting build directory of my aur helper. Do you think it is worth to make package that would be same just download the tarballs?

haawda commented on 2020-12-21 15:23 (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.

WorMzy commented on 2020-12-21 12:37 (UTC)

@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.

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