33.5.0 launches black windows (on an OLD Mac) Topic is solved

[KlarkKentThe3rd]

This is less of a real complaint, and more me realizing the sad news. Latest PM no longer works on my old Mac.

I do have a >>newer<< Mac, so it should run on that one definitely. I am not REALLY asking for any fixes, if it is too much trouble. Sometimes the hardware is too old, and there is no fixing that. I am mainly on my older computer since it has a slightly larger screen, and I prefer large laptops in general. If some PM security update is crucial, I will switch to my smaller but newer laptop for daily use.

For reference, the OS on my OLD computer is 10.15.7 the CPU is 2.6 GHz Quad-Core Intel Core i7 and integrated GPU is ntel HD Graphics 4000 1536 MB (it's a mid 2012 model).

[dbsoft]

Can you try this build instead: https://dbsoft.org/palemoon/palemoon-33 ... nosign.dmg

[KlarkKentThe3rd]

Can you try this build instead: https://dbsoft.org/palemoon/palemoon-33 ... nosign.dmg

Are you a wizard?

No, seriously, WHAT is different about your build? Is it really just a lack of signature? When you answer this question I will mark thread as solved.

[dbsoft]

Yes only difference is the lack of a signature... ugh... I was hoping the ad hoc one was the solution, but I guess it has problems too.

[KlarkKentThe3rd]

Yes only difference is the lack of a signature... ugh... I was hoping the ad hoc one was the solution, but I guess it has problems too.

I guess a signature somehow makes my computer decide to disable the GPU (so NOTHING is displayed in windows).

[Moonchild]

I guess the only solution would be to have a signed and an unsigned version -- and tell people which version they need (I'm assuming there's a specific cut-off version for the problems)

[dbsoft]

I guess the only solution would be to have a signed and an unsigned version -- and tell people which version they need (I'm assuming there's a specific cut-off version for the problems)

Well, if I do dual Intel versions, I would do an unsigned version for pre-MacOS 11 (10.7 to 10.15) and a signed and notarized version for 11-15 like we do with ARM.

That way on 11 and later they can avoid the "Open Anyway" step and "Unidentified Developer" message.

Edit: Going to wait for the 15.2 release and see if that fixes the problem before making any decisions, it should be out this month.

[Moonchild]

Well, if I do dual Intel versions, I would do an unsigned version for pre-MacOS 11 (10.7 to 10.15) and a signed and notarized version for 11-15 like we do with ARM.

That way on 11 and later they can avoid the "Open Anyway" step and "Unidentified Developer" message.

Yes, I was hoping that would be possible

[CHris Hitarori]

Interestingly, on an even older Mac (10.11 El Capitan) the signed version 33.5.0 downloaded from the official website works without a problem. Maybe that one's too old to even check for the signature?

@dbsoft Should I test different versions again?

[dbsoft]

Prior to release I tested the ad hoc signed version on the following versions: 10.7, 10.10, 10.11, 12, 13, 14 and 15 without problems.

I had hoped it wouldn't have issues, wasn't really expecting the problem to be on 10.15. But honestly it has been so long since I tried last that I can't remember which versions were having issues.

((The signed and notarized one failed on 10.7 and I stopped testing it at that point))