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!)

Yes, that's certainly not normal. The only other time I've seen anything similar is with Pale Moon, related to the checksum, not the developer signature, but only on update. There, it's considered not only legitimate but necessary to Accept Modification. As I said, since this wasn't happening at the Mini, just the iMac with High Sierra I brought over the app, Profile and Little Snitch rules, which was a solution. Doubtful it was the app, which was exactly the same, so that leaves the profile and LS. I'm wondering if anyone has any idea what could have provoked this, which I've never encountered before, either on Dynasty or on regular Firefox esr - or, for that matter, any version of Firefox. And, not to forget, I had been running the Dynasty at the iMac, with nothing having changed, profile, app, LS rules when suddenly this started happening.

EDIT: with some research, discovered that this is explicitly related to Little Snitch:

Connection alert - Warnings

help.obdev.at help.obdev.at

Advanced topics - Process identity checks

help.obdev.at help.obdev.at

pale moon accept modification.png
 
Last edited:
There was a beta i3Roly wanted testing to see if Spotify was now working. Where do I find that beta, in other words under Releases which one is that particular beta?

I ask because I thought I'd test it with my High Sierra VM (so as not to disturb the Dynasty profile(s) in my High Sierra host). The Spotify discussion has somehow disappeared from Issues on GitHub.

@Wowfunhappy .
 
Wowfunhappy said:
I honestly don't remember, I think we're okay on Spotify.
Click to expand...
Well, sort of! I downloaded the latest Dynasty to my High Sierra VM, opened the Spotify web version, and I was able to login , do searches, and see lists of album tracks with their Play buttons, etc. Unfortunately, I'm getting the 'Spotify is not able to play this right now' message that so many have complained about.
 
Firefox Dynasty 143 is here - give it a try.

I loaded it on Mac OS X 10.11.6 El Capitan and it runs without any problems.
 
Has FF Dynasty dropped macOS 10.7? I'd been running it just fine on 10.7, except for the transparent extension icons problem, which was negligible. Today, I downloaded 143.0.1, and it opened to blank viewports. What I mean is I see my toolbar and a theme, but the URL bar is blank, and there's no on-page content. 142.0.2 is OK.
 
Last edited:
Is FD 144 crashing on exit for anyone else? On my Macbook5,2 with MacOS Mojave 10.14.6, it crashes on exit for the Wikipedia website, though I sometimes have to look at a few pages first. I choose Quit on the menu, nothing happens, then I choose Quit right-clicking the Dock icon, it crashes, and displays a Mozilla crash report dialog. Sometimes it hangs and I have to Force Quit, which displays a MacOS crash dialog.

It may have started with FD 143. I only use FD for websites that don't work in FF 115. Separate profiles, so no contamination.

I've been trying to force a crash to get a report I can attach, and now it's not crashing. Typical.
 
Yes, same here!
Also, keyboard shortcuts (Cmd+T, Cmd+W, Cmd+Q etc.) fail to work after a while, and I can't work out why. Frustrating to be honest 😥
Unibody MacBook with Mojave, but on the exact same system on an iMac i3 it works fine.

Cheers :)

Hugh
 
Crash report attached below...

Cheers :)

Hugh
 

Attachments

  • Crash Report Firefox Dysentery.rtf.zip
    7.5 KB · Views: 5
Hughmac said:
Crash report attached below...

Cheers :)

Hugh
Click to expand...
nospamboz said:
Finally caught one. Mine is similar.
Click to expand...
Yes, both of these are pointing to the same problem! The key is NSInvalidArgumentException: -[NSView hasRepresentedView]: unrecognized selector sent to instance

Can one of you please open a Github issue and attach the crash report and the first version with the issue? This should be straightforward to fix.
 
I think I've found a cure, by repairing permissions in Terminal the issue has stopped occurring (so far) ;)

Code: 
sudo diskutil resetUserPermissions / `id -u`

Cheers :)

Hugh
 
  • Like
Reactions: MBAir2010
Hughmac said:
I think I've found a cure, by repairing permissions in Terminal the issue has stopped occurring (so far) ;)

Code: 
sudo diskutil resetUserPermissions / `id -u`

Cheers :)

Hugh
Click to expand...
...I mean, if it works then great, but your crash log indicated something a permissions repair wouldn't going to fix. Firefox Dynasty was trying to call a method that doesn't exist on your OS.
 
I'm sorry I don't have a GitHub account so can't submit issues, but I give permission for you to do so if it's OK.
However it's probably specific to my Unibody Macbook A1342 running dosdude1 patched Mojave, as my i3 iMac 20.5" (also patched to run Mojave) has no such troubles with FireFox Dynasty.

Cheers :)

Hugh
 
Hmm, well I didn't realize you were running a hardware-unsupported OS, can anyone replicate running an OS officially supported on their hardware?
 
It may be that @nospamboz is also running a patched OS on a MacBook 5,2 whereas I am doing the same on a MacBook 7,1 ;)
If we are the only two with this issue then I suggest that @nospamboz tries my permissions fix.

Cheers :)

Hugh
 
Hughmac said:
It may be that @nospamboz is also running a patched OS on a MacBook 5,2
Click to expand...
That is indeed the case, but there's a "complication".

The Dosdude1 Mojave install patches the graphics system to work on non-Metal. Some months ago I tried adding a different graphics patch, which broke my system, which I fixed by re-installing the Dosdude1 patch. I had forgotten that I had already needed to patch his patch with the High Sierra AppleGVA. This weekend I restored that patch.

So far since that patch, I have been unable to reproduce the FFD crash. I'll keep trying and will report back with a result.
 
  • Like
Reactions: Hughmac and MacMorrison
maverick28 said:
Has FF Dynasty dropped macOS 10.7? I'd been running it just fine on 10.7, except for the transparent extension icons problem, which was negligible. Today, I downloaded 143.0.1, and it opened to blank viewports. What I mean is I see my toolbar and a theme, but the URL bar is blank, and there's no on-page content. 142.0.2 is OK.
Click to expand...
Sorry I missed this, but yes 10.7 support is gone. https://github.com/i3roly/firefox-dynasty/issues/82
 
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