AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Pale moon could not find mozilla runtime11/7/2023 ![]() Bug #982974 - Be paranoid about neutering ArrayBuffer objects. Bug #983344 - JavaScript: Simplify typed arrays and fix GC loops. Bug #982906 - Remove option for security bypass in URI building. Bug #982957 - Fix crash if certain sweeps run out of memory. ![]() Bug #982909 - Consistently use inner window when calling OpenJS. Pale Moon also provides a ton of proprietary browser extensions on its site, and it’s still compatible with legacy XUL add-ons if you were disappointed when Firefox got rid of XUL functionality, you can still add all of your favorite extensions to Pale Moon. ![]() Bug #896268 - Use a stateless approach to synchronous image decoding. Bug #940714 - Add an RAII class to make synchronous raster image decoding safer. Feature update: Selecting "Warn me when closing multiple tabs" in the Options window will now apply both to closing a window and closing other tabs in the tab bar. There may have been a few other, similar small usability bugs in the same code that have now been fixed. Bugfix: the new status bar code in 24.4.0 had a bug, preventing the downloads panel/window from opening when clicking on the download status indicator. We have no plans to drop any older currently used compilers or linux 32bit capability on a build level but it is on a "Best Effort" basis in regards to testing and patches going forward and the community may need to give a care and a hand keeping it up to snuff.Palemoon v24.4.1 () released. Do a clean reinstall and delete the Firefox program folder before (re)installing a fresh copy of the current Firefox release. Of course, individuals can always build whatever the fuck they want for their, and only their, use. ![]() Leaving out old and insecure distros completely. It helps shift our release engineering and support burden from all linux to just those still with active and supported 32bit development. This serves as an incentive to leave 32bit Linux behind broadly but allows the flexability for distro targeted builds if there is someone dedicated enough to provide not only a package for any specific distro still doing 32bit but also to provide the support to go along with it. It is also not caused only by bash: any "exec-like" procedure that does not allow setting the 0th arguments will cause failures in XPCOM (or whatever program you use that does something similar.)Īs has been written elsewhere we have ended the generic 32bit binary we provide and won't be approving any 32bit 3rd party generic builds either nor any bastardized binary repack BUT we will allow proper from source built system packages that specifically target 32bit distros such as in the case of the debian-based ones Steve is doing which are in no way generic to all of linux. Since the wrapper does not have the proper path, the process won't find the runtime. While I don't know the exact steps taken by XPCOM, as I don't know where in the code initialization happen, the reason why it does not work should be because the 0th argument passed to the "exec'd" process, that is, the process name, is not the full path to the real Pale Moon binary, but to the wrapper. There are only a handful of programs behaving like that, and Pale Moon is probably the most "end user" one, meaning that most people don't even think about this caveat. Click on the icon of the extension in the Status Bar, and replace the Useragent string with Mozilla/5.0 (Windows NT 10.0 Win64 圆4 rv:100.0) Gecko/20100101 Firefox/100.0. It will trip up any program using "itself" to find some file, like how XPCOM does to find the runtime.īy "itself" I mean that the program uses the process name taken at runtime, rather than a hardcoded path, to find the necessary resources to initialize itself. This isn't specific to UXP, if I understood what OP is trying to do. ![]()
0 Comments
Read More
Leave a Reply. |