LSOpenURLsWithRole() failed with error 54 on OSX 15.1.1
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
People
(Reporter: monochromec, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36 OPR/115.0.0.0
Steps to reproduce:
- Downloaded the dmg and installed the software
Actual results:
When trying to open SM on this platform results in the above error on 15.1.1 running on an M1.
SIP is enabled, and startup security policy is set to "Full Security".
Logs analysis inconclusive so far. Happy to provide more info if required.
Expected results:
SM starts normally.
![]() |
||
Comment 1•2 months ago
|
||
I suspect it is a duplicate of bug 1924612. Apple broke running unsigned application in 15.1 and has not fixed it yet. Workaround in Bug 1924612.
IF it is a different bug happy to deduplicate it but it will probably go nowhere unless someone points out a solution. No time and resources to set up notarization for now.
Signing the app bundle as a work-around as outlined in # 1924612 does indeed solve the issue.
The question of course remains: Why are app bundles not signed in the first place before packaging them into a dmg? The build infrastructure for this must be in place; otherwise other Mozilla products including FF and TB would face the same issue.
![]() |
||
Comment 3•2 months ago
|
||
SeaMonkey is not a mozilla product. We are still allowed to used bugzilla and the source is partially hosted in an MZLA repo but how long is anyones guess. We hav no access to taskcluster for building and use our own signing key on Windows. It is basixally a shoebox operation.
The real question is why apple does not fix this bug. Other projects and anyone using small scale development or just a quick test build are affected.
It's a two-edged sword. Without going into the details, I see Apple's requirement to provide a secure infrastructure for program execution and thus a certain vetting level of applications. Esp. for apps not provided by official sources allowing a pre-deployment checking of apps such as the App Store. On the other side it may make things overly complicated as we just experienced with this issue.
Would could be more helpful of course is a way more descriptive error message as to why this app bundle could not be executed instead of this cryptic one-liner. 🙄
Description
•