Package Details: palemoon

Git Clone URL: (read-only)
Package Base: palemoon
Description: Open source web browser based on Firefox focusing on efficiency.
Upstream URL:
Keywords: browser goanna web
Licenses: GPL, MPL, LGPL
Submitter: artiom
Maintainer: WorMzy
Last Packager: WorMzy
Votes: 121
Popularity: 1.783259
First Submitted: 2014-06-05 10:54
Last Updated: 2019-07-04 22:45

Latest Comments

1 2 3 4 5 6 ... Next › Last »

tony.aln commented on 2019-07-13 17:59

Thank you for the consideration. Of course, I will inform you if there are any issues.

WorMzy commented on 2019-07-09 11:48

Thanks for formatting. Is there anything else useful in the referenced log file and/or the system journal? Can you reproduce the problem with palemoon-bin?

I note you're using the intel video driver, if it's an option for your system, see if you can reproduce the problem with the modesetting driver.

syrenity commented on 2019-07-08 18:43

Formatted, worth saying there is a new glibc and lib32-glibs update, wonder if resolves the issue.

WorMzy commented on 2019-07-07 16:55

Thanks for investigating. I've successfully built with your proposed changes, and tested that the browser launches with this build. I'm happy to introduce this change the next time upstream makes a release, but if you're running your build and encounter any issues between then and now, please let me know.

tony.aln commented on 2019-07-07 15:37

I had some time to read and try some stuff. So, GCC 9's -Werror=format-overflow warning is being treated as an error and aborting the build. From gcc's online documentation (available at :

"Warn about calls to formatted input/output functions such as snprintf and vsnprintf that might result in output truncation. When the exact number of bytes written by a format directive cannot be determined at compile-time it is estimated based on heuristics that depend on the level argument and on optimization. While enabling optimization will in most cases improve the accuracy of the warning, it may also result in false positives. Except as noted otherwise, the option uses the same logic -Wformat-overflow."

Therefore, by enabling lto by using -flto=2(cpu thread number), gcc9 analyzed the code better, didn't give the warning nor need the fix and produced a space net change savings of about 10MiB in comparison with the same version without lto, performance benefits are not known (it feels faster but it may be just placebo, I have to see how to quantify and display the performance gains) and a negligible amount less of time to build, but used more ram to build. Without lto it's a warning and the warning can be disabled with -Wno-format-overflow in the CPPFLAGS variable in: PKGBUILD

like this: export CPPFLAGS="$CPPFLAGS -O2 -Wno-format-overflow"

and in the like this: ac_add_options --enable-optimize="-O2 -Wno-format-overflow"

The build progresses smoothly with gcc9 by just adding that and by commenting the gcc8 CC and CXX export lines at the beginning of mozconfig and removing gcc8 dependency from the PKGBUILD. Please, feel free to reproduce the fix provided and hopefully instate the needed changes so others can build with gcc9 smoothly as well. Enjoy. Edit1: fixed formatting Edit2: fixed space savings wording Edit3:fixes

WorMzy commented on 2019-07-05 09:25

Please use markdown to format your post, syrenity. Three backticks before and after the output should make it into a readable code block.

syrenity commented on 2019-07-04 22:43

[  7931.122] (EE) Backtrace:
[  7931.122] (EE) 0: /usr/lib/Xorg (xorg_backtrace+0x4d) [0x55c7efcc30cd]
[  7931.122] (EE) 1: /usr/lib/Xorg (0x55c7efc12000+0xb1209) [0x55c7efcc3209]
[  7931.122] (EE) 2: /usr/lib/ (0x7f1fe5f85000+0x3a7e0) [0x7f1fe5fbf7e0]
[  7931.122] (EE) 3: /usr/lib/ (gsignal+0x145) [0x7f1fe5fbf755]
[  7931.122] (EE) 4: /usr/lib/ (abort+0x125) [0x7f1fe5faa851]
[  7931.122] (EE) 5: /usr/lib/ (0x7f1fe5f85000+0x7ca38) [0x7f1fe6001a38]
[  7931.122] (EE) 6: /usr/lib/ (0x7f1fe5f85000+0x8325a) [0x7f1fe600825a]
[  7931.122] (EE) 7: /usr/lib/ (0x7f1fe5f85000+0x84c5c) [0x7f1fe6009c5c]
[  7931.122] (EE) 8: /usr/lib/xorg/modules/drivers/ (0x7f1fe44df000+0x5992f) [0x7f1fe453892f]
[  7931.122] (EE) 9: /usr/lib/Xorg (0x55c7efc12000+0x12d3ae) [0x55c7efd3f3ae]
[  7931.122] (EE) 10: /usr/lib/Xorg (0x55c7efc12000+0xfd945) [0x55c7efd0f945]
[  7931.122] (EE) 11: /usr/lib/Xorg (0x55c7efc12000+0x10e275) [0x55c7efd20275]
[  7931.122] (EE) 12: /usr/lib/Xorg (0x55c7efc12000+0x15ceee) [0x55c7efd6eeee]
[  7931.122] (EE) 13: /usr/lib/Xorg (FreeResource+0xcd) [0x55c7efd6f18d]
[  7931.122] (EE) 14: /usr/lib/Xorg (0x55c7efc12000+0x17ab6e) [0x55c7efd8cb6e]
[  7931.122] (EE) 15: /usr/lib/Xorg (0x55c7efc12000+0x37fe8) [0x55c7efc49fe8]
[  7931.122] (EE) 16: /usr/lib/ (__libc_start_main+0xf3) [0x7f1fe5fabee3]
[  7931.122] (EE) 17: /usr/lib/Xorg (_start+0x2e) [0x55c7efc4a30e]
[  7931.122] (EE) 
[  7931.122] (EE) 
Fatal server error:
[  7931.122] (EE) Caught signal 6 (Aborted). Server aborting
[  7931.122] (EE) 
[  7931.122] (EE) 
Please consult the The X.Org Foundation support 
 for help. 
[  7931.122] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[  7931.122] (EE) 
[  7931.122] (II) AIGLX: Suspending AIGLX clients for VT switch
[  7932.335] (EE) Server terminated with error (1). Closing log file.

syrenity commented on 2019-07-04 22:40

Latest version randomly crashes X server on Dell XPS 15 (9570).

Had to stop using it for the meanwhile.

tony.aln commented on 2019-07-04 20:09

huh, I built them without any patches or weird flags, and I read that thread a while back too. What I did was remove ggc8 from the PKGBUILD and the mozconfig and voilà. That gentleman on the thread is the one which is building pale moon with gcc9 right now for fedora which I mentioned before. I'm gonna try on some boxes without -flto to see if I can succeed building it.

WorMzy commented on 2019-07-04 11:25

I got a build failure with gcc9 (the same build failure that upstream was aware of in March) which is why I've switched to gcc8 in the mozconfig.

I'd rather not include patches to make the package build with gcc9, as upstream get really arsey about that sort of thing, and it's not worth dealing with their antics. The best thing you can do is make noise on their bug tracker about it (but don't expect anything to change).