https://bugs.documentfoundation.org/show_bug.cgi?id=172229
--- Comment #8 from [email protected] --- (In reply to Alex Thurgood from comment #7) > (In reply to jedchase from comment #3) > > > > The LibreOfficePython interpreter is signed for use as a bundled child > > process within LibreOffice.app; Tahoe 26.5 appears to be enforcing a Launch > > Constraint that prevents it from being invoked directly by Terminal/zsh as a > > parent process. The crash occurs before the interpreter loads any code at > > all — no import uno, no script execution. This is purely a launch-time > > code-signing check. > > This breaks the documented path for external Python automation against LO > > via UNO socket on Tahoe (anyone whose external Python script previously used > > /Applications/LibreOffice.app/Contents/Resources/python would now fail with > > this signal). System Python or Homebrew Python may still work if it can be > > configured to find LO's UNO modules — I haven't been able to test that yet. > > This behaviour has already been reported as bug 167752 > > A deliberate change was introduced into the Mac build to have a launch > constraint which prevents launch of the included python, cf. comment 5. > > It appears to remain as yet unresolved. Hi Alex, Thanks for taking a look, and for the pointer to bug 167752 - I hadn't come across it. It's helpful to know that the Terminal-launched Python crash I described in comment 3 is already tracked there, and that the constraint is believed to be set in the LibreOffice build, as comment 5 on that report describes. As I said in my comment, I mentioned it as a side finding while looking for workarounds, not because I think it's the same bug as the in-process save hang. I believe the main problem in this report is a different one, for a practical reason: my setup was working just fine this spring. Comment 5 on 167752 dates from October 2025, and I set up my extension months after that, in March 2026. I then used it daily, saving documents through the extension without any trouble, across several Tahoe releases (26.0 through 26.4) and LibreOffice 26.2.x updates, until mid-May. So the launch constraint described there was already in the builds I was running, and it can't be what broke my saves. It also doesn't involve launching the bundled Python from outside LibreOffice at all: the Python code runs inside LibreOffice as an OXT extension, so LibreOffice is the parent process. What hangs now is storeToURL, .uno:Save and non-hidden loadComponentFromURL called from the extension's background thread, while in-memory UNO calls from that same thread still work. The minimal repro is attachment 207208. As noted in the report, Tahoe 26.5 and LibreOffice 26.2.3.2 arrived within a day or two of each other, so I can't say yet which of the two triggered the hang. So the two may be similar in spirit (macOS tightening something that Python extensions relied on), but I don't think they are the exact same bug. Would it make sense to keep this one open separately? I'm happy to add 167752 under See Also if you think that would be useful, and to test anything that would help tell the two apart. Thanks again!! -- You are receiving this mail because: You are the assignee for the bug.
