https://bugs.documentfoundation.org/show_bug.cgi?id=144902
--- Comment #23 from Mike Kaganski <[email protected]> --- (In reply to ywupub from comment #21) > Is it possible that the files have been installed but can't be run? So I > attached libreoffice dir tree to let you check if there are files missing or > not-working? Yes, everything looks OK in the tree. And yes, it looks that something prevents python from running on your system. May it be antivirus? Or some other security engine? I can't suggest you something specific to try, just some general direction of investigation. You might also try Process Monitor from Sysinternals to try to monitor soffice.bin from the point before the crash until the crash, and check if there's something suspicious in the output - failures to launch executables, file not found (there will be lots of legitimate "file not found" cases...). I can only tell that I have tested that failure to load "pythonloader" and "uno" modules (in getLoaderModule [1] and importUnoModule [2]), as happens on your system, does crash the program. I can't tell why it may happen, though. Removing LibreOffice from Program Files, and user profile, removes every setting specific to LibreOffice configuration on your system - so it is something external. And you also have checked that the UCRT system library, along with VC redist, are re-installed. [1] https://opengrok.libreoffice.org/xref/core/pyuno/source/loader/pyuno_loader.cxx?r=c099288c#84 [2] https://opengrok.libreoffice.org/xref/core/pyuno/source/module/pyuno_runtime.cxx?r=05bc93db#17 -- You are receiving this mail because: You are the assignee for the bug.
