Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Other Firefox Dynasty - Firefox for OS X 10.8+ (Also, Web App Templates!)

I've now completed my first round of testing, attempting to upgrade Dynasty v. 135.01 via direct downloads from Github (i.e., not using the downloader pref pane, which I have not yet reinstalled - also FWIW, these downloads were all accomplished in Pale Moon, from which I am also posting this reply). I have the following results:

Version 136.01: downloaded, installed (by replacing/overwriting the older version), and launched without issue.​
​
Version 137.0b5: Downloaded, installed (same way), and launched without issue.​
​
Version 137.02: Here's where it hung up. Downloaded & installed as per the above, but would not launch. By all appearances, same problem as before.​
​
That's where I'll stop for today. More testing to come. Thanks again all!

EDIT May 15, 2025: This issue has been resolved. See Post #138.
 
Last edited:
@Raging Dufus Please write this up in a Github issue including detailed hardware information and if possible a screen recording for i3roly. He generally really dislikes getting bugs he can't reproduce, but I think that since you've found the first version where it breaks, he'll have something to go off of.
 
Wowfunhappy said:
@Raging Dufus Please write this up in a Github issue including detailed hardware information and if possible a screen recording for i3roly. He generally really dislikes getting bugs he can't reproduce, but I think that since you've found the first version where it breaks, he'll have something to go off of.
Click to expand...
I'll do that if I can't resolve it on my own. But Dynasty falling down on me @ v. 137.02 is curious, because 137.02 is the version I was using, without issue, before I ever had the problem in the first place (back before I reinstalled Mavericks). My problems first started when I tried upgrading 137 to 138. So I'm not sure I have identified the version where things break down for me - it may not be a version-specific problem at all. More testing will tell. Thanks!

EDIT May 15, 2025: This issue has been resolved. See Post #138.
 
Last edited:
Wowfunhappy said:
Probably not. On Lion there is a specific bug in the kernel which Firefox was triggering. The bug is still there (and it probably does exist on Snow Leopard too), but i3roly found a way to avoid triggering it.

This type of thing is an absolute last resort when there appears to be no other option. Obviously for Firefox Dynasty there was another option, but we didn't know that at the time.
Click to expand...
ohh, alright. thank you! still super happy that SL will soon be able to use modern sites faster.
 
UPDATE: I’m posting this from a successfully installed and working Firefox Dynasty v. 137.0.1 (which as you can see reports itself as “Firefox 137.0.2” - a discrepancy also noted by others here):

Untitled.jpg

Anyway, this seems to be as far as I can go right now. I repeated the steps used in Post #111 above with almost every version of Dynasty between 135.0.1 and the latest release, 138.0.1. Nothing after this one will launch, so it does seem to be a version-specific problem beginning with the download labeled FIREFOX_137_0_2_RELEASE and carried forward from that point.

As suggested by @Wowfunhappy, I did create a Github issue for this problem. I’m also pleased to report that Wowfunhappy’s downloader pref pane seems to have nothing to do with the issue, since the versions that work or don’t work on my machine display the same behavior whether downloaded directly or via the pref pane.

I’m letting this go for now. Hopefully the developer will be able to correct the issue, but if not I’ll continue using this version and be happy about it. Thanks again everyone for your help. :)

EDIT May 15, 2025: This issue has been resolved. See Post #138.
 
Last edited:
Some weird stuff is going on in Firefox Dynasty on Lion when playing videos from FB, YouTube and, possibly, other platforms. As you play a clip, the video stream appears as a red background with only audio available. Striking along the playback timeline bar reveals thumbnails containing the actual frames. However, all you see is that red background. When you click the notification bell, the video becomes normal for a fraction of a second, obscured by the menu. Once the notification pop-up list goes, so does the video.
 
I made a screen recording of what happens when I try to update Firefox Dynasty 137_0_1 (which works on my MBP) to 137_0_2 (which doesn't), to hopefully enlighten people responding to my Github issue. I couldn't get it uploaded there, but it would upload here, so if you're interested please see attached.

EDIT: Adding other screen recordings as requested on Github. Hiding these behind a spoiler to try and minimize the impact on this thread.




EDIT May 15, 2025: This issue has been resolved. See Post #138.
 
Last edited:
maverick28 said:
Some weird stuff is going on in Firefox Dynasty on Lion when playing videos from FB, YouTube and, possibly, other platforms. As you play a clip, the video stream appears as a red background with only audio available. Striking along the playback timeline bar reveals thumbnails containing the actual frames. However, all you see is that red background. When you click the notification bell, the video becomes normal for a fraction of a second, obscured by the menu. Once the notification pop-up list goes, so does the video.
View attachment 2510349
Click to expand...
Have you tried going into Settings → Performance → Uncheck "Use recommended performance settings" → Uncheck "Use hardware acceleration when available"?


(I assume this would disable hardware accelerated video decoding, but if not there's a chance you'll also need to tweak an about:config flag.)
 
Guys Good morning! I can't open this face on Osx Lion, would you have any secret or recent version? I downloaded several versions but to no avail, it shows the open icon but freezes the screen and does not climb the window to navigate.
 
Raging Dufus said:
…what happens when I try to update Firefox Dynasty 137_0_1 (which works on my MBP) to 137_0_2 (which doesn't), to hopefully enlighten people responding to my Github issue.
Click to expand...
My Github issue is now closed, because it was resolved by i3roly (Firefox Dynasty developer). Seems the problem was the Santa Rosa C2D processor in my 2007 MBP being unable to handle the version of Rust that originally shipped with v. 137_0_2. When he recompiled with (I presume) an earlier version of Rust, voila! It worked.

Of note: I also have a 2008 MBP w/Penryn C2D which was unaffected by this issue. Practically the only difference between that machine and my 2007 is the CPU. Even the graphics card is the same. So it’s a pretty good bet that my issue was isolated to the processor architecture. But in any event, it’s solved!

If you’re experiencing problems with Firefox Dynasty on a Santa Rosa-powered 2007 Mac I strongly suggest upgrading to the latest (as of this post) version, listed on the download page as FIREFOX_138_03_RELEASE.
 
  • Like
Reactions: Grumpus, DurltazorOSXPower, wicknix and 1 other person
DurltazorOSXPower said:
Guys Good morning! I can't open this face on Osx Lion, would you have any secret or recent version? I downloaded several versions but to no avail, it shows the open icon but freezes the screen and does not climb the window to navigate.
Click to expand...
If Firefox is running and hanging, force-quit it. In the Terminal, navigate to the Firefox binary subdirectory:

Bash: 
app=$(mdfind -onlyin /Applications/  "kMDItemFSName == 'Firefox' || kMDItemFSName == 'Firefox.app' || kMDItemDisplayName == 'Firefox' || kMDItemDisplayName == 'Firefox.app'") ; cd "$app"/Contents/MacOS/

Execute this command to open FF in Safe Mode:

Bash: 
./firefox --safe-mode

Open the Preferences and uncheck "Recommended Performance Settings" and "Use hardware acceleration". Relaunch Firefox.
 
maverick28 said:
If Firefox is running and hanging, force-quit it. In the Terminal, navigate to the Firefox binary subdirectory:

Bash: 
app=$(mdfind -onlyin /Applications/  "kMDItemFSName == 'Firefox' || kMDItemFSName == 'Firefox.app' || kMDItemDisplayName == 'Firefox' || kMDItemDisplayName == 'Firefox.app'") ; cd "$app"/Contents/MacOS/

Execute this command to open FF in Safe Mode:

Bash: 
./firefox --safe-mode

Open the Preferences and uncheck "Recommended Performance Settings" and "Use hardware acceleration". Relaunch Firefox.
Click to expand...
Perfect man , it's work now !! thanks
 
Will post as new issue at https://github.com/i3roly/firefox-dynasty/issues, if warranted:


Seeing that there are 3 critical fixes for Firefox ESR (two of which appear to be zero days) and I assume any Firefox Desktop version as well. Wondering if the latest release the [FIREFOX_139_0_BUILD1](https://github.com/i3roly/firefox-dynasty/releases/tag/FIREFOX_139_0_BUILD1) includes these fixes?

www.mozilla.org

Security Vulnerabilities fixed in Firefox ESR 115.23.1

www.mozilla.org www.mozilla.org

thehackernews.com

Firefox Patches 2 Zero-Days Exploited at Pwn2Own Berlin with $100K in Rewards

Mozilla patched 2 Firefox zero-days exploited at Pwn2Own Berlin, risking code execution via JavaScript flaws.
thehackernews.com thehackernews.com

Currently running the 138.0.4, which I believe was released well in advance of these fixes, and which I'm guessing may not be safe.

Screen Shot 2025-05-21 at 10.45.30 AM.png
 
RK78 said:
Will post as new issue at https://github.com/i3roly/firefox-dynasty/issues, if warranted:


Seeing that there are 3 critical fixes for Firefox ESR (two of which appear to be zero days) and I assume any Firefox Desktop version as well. Wondering if the latest release the [FIREFOX_139_0_BUILD1](https://github.com/i3roly/firefox-dynasty/releases/tag/FIREFOX_139_0_BUILD1) includes these fixes?

www.mozilla.org

Security Vulnerabilities fixed in Firefox ESR 115.23.1

www.mozilla.org www.mozilla.org

thehackernews.com

Firefox Patches 2 Zero-Days Exploited at Pwn2Own Berlin with $100K in Rewards

Mozilla patched 2 Firefox zero-days exploited at Pwn2Own Berlin, risking code execution via JavaScript flaws.
thehackernews.com thehackernews.com

Currently running the 138.0.4, which I believe was released well in advance of these fixes, and which I'm guessing may not be safe.
Click to expand...
It looks like the equivalent non-ESR fixes landed in Firefox 138.0.4: https://www.mozilla.org/en-US/security/advisories/mfsa2025-36/
 
Wowfunhappy said:
It looks like the equivalent non-ESR fixes landed in Firefox 138.0.4: https://www.mozilla.org/en-US/security/advisories/mfsa2025-36/
Click to expand...
Seeing those fixes now in the 138.0.4 Dynasty. But question still lingers, would those fixes apply to the actual Dynasty version, which, as always, links, when finally ready, to the Mozilla release notes, when in fact the Dynasty version may not really include those fixes? As I mentioned earlier, what prompts this lingering doubt is that the Dynasty 138.0.4 I installed was released on 5/14, earlier than the 5/19, the actual Firefox release date. Or is possible that i3roly got such a valid jump on this?
 
Wasn't really asking why the Dynasty release was so much earlier than the Mozilla one. Have seen this often before; generally have no problem with it.

Bottom line question needing a yes or no answer: does the 138.0.4 Dynasty released/installed ~5 days before the actual Mozilla release - release notes not yet even prepared, per usual - include the patches for the critical security vulnerabilities/zero days already discussed?

Hard to understand that Mozilla would wait 5 days before this critical update. Obviously, don't want to use an unpatched Firefox release for something so serious. Perhaps I should be asking i3roly directly?
 
Last edited:
RK78 said:
Bottom line question needing a yes or no answer: does the 138.0.4 Dynasty released/installed ~5 days before the actual Mozilla release - release notes not yet even prepared, per usual - include the patches for the critical security vulnerabilities/zero days already discussed?
Click to expand...
Because this is a critical security vulnerability, the actual tickets on Bugzilla aren't accessible to the pubic as of this writing. This means that I can't check "oh, here is the specific commit that fixed the vulnerability, here is when it got merged into Firefox Dynasty." Mozilla is keeping that information under wraps.

I can tell you that the fix landed in Firefox 138.0.4 according to Mozilla, so a version of Firefox Dynasty based on version 138.0.4 or later should have the patch included. That's all that anyone will reasonably be able to tell you based on the information Mozilla has released. (By the way, this also means mainline Firefox had the fix three days before ESR.)

If you need the absolute best security, you should upgrade to an officially supported version of macOS and use an official release of a mainstream web browser.

Otherwise, I'm pretty sure the fix is present in the "Firefox_138_0_3_107VIDEO_HOTFIX" build of Firefox Dynasty (which is actually Firefox 138.0.4 due to how Firefox releases work). My recommendation is that you use that right now, then upgrade to the next release version of Firefox Dynasty when it is available.
 
Last edited:
  • Like
Reactions: wicknix
If you are that worried about it i would advise staying offline. Pretty sure most of us running unsupported OS’s aren’t worried about some patches that may or may not be in Dynasty at the current moment. If it is, it is. If not, it will be patched in a few days.
 
  • Like
Reactions: Raging Dufus
This, which I even mentioned on my first post on this topic, surely includes the latest security fixes.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back