https://bugs.documentfoundation.org/show_bug.cgi?id=172229
--- Comment #3 from [email protected] --- Follow-up: investigating an external-process workaround tonight (using the standard --accept=socket,host=localhost,port=2002;urp; UNO listener, launched fresh from Terminal with no documents pre-loaded), I encountered a related macOS Tahoe 26.5 enforcement issue that may be relevant to the broader picture. Attempting to run LibreOffice's bundled Python interpreter directly from Terminal — /Applications/LibreOffice.app/Contents/Resources/python — to connect to the LO instance via UNO socket results in the Python interpreter being killed by macOS before any user code executes. Crash report excerpt: Process: LibreOfficePython Version: 3.12.13 Exception Type: EXC_CRASH (SIGKILL (Code Signature Invalid)) Termination Reason: Namespace CODESIGNING, Code 4, Launch Constraint Violation parentProc: zsh responsibleProc: Terminal 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. I mention this not because I think it's the same bug as the in-process OXT save hang, but because the timing (regression appears with Tahoe 26.5) and the underlying mechanism (Tahoe-side enforcement of constraints that LO's existing code wasn't expecting) suggest both may be downstream effects of the same Tahoe security tightening. The full crash report is available if helpful. -- You are receiving this mail because: You are the assignee for the bug.
