I've added debug print of sys.path to the abc.py and it indeed shovels in the local path even on the execution:įile "/home/scarabeus/tmp/lotest/abc.py", line 3, in īut if we comment out that ~/tmp/lotest $ lowriter Maybe their helper scripts (lowriter/.) reset the pythonpath. This is all handled in the pyuno code pyuno/source/loader/pyuno_loader.cxx so I will try to figure out whats going on and why others do not trigger it. So this shows us we don't have trouble with the script wrappers but some behaviour is wrong directly in the compiled code.īut if I override the PYTHONPATH it seems to work just ~/tmp/lotest $ PYTHONPATH="/home/" ~/tmp/lotest $ PYTHONPATH="/home" /usr/lib64/libreoffice/program/soffice -writer NameError: name 'hello' is not ~/tmp/lotest $ /usr/lib64/libreoffice/program/soffice -writer If it is not reproducible with the upstream package then we have some issue with what files are checked upon execution and it seems it takes $pwd into account (or ~/tmp/lotest $ lowriterįile "/home/scarabeus/tmp/lotest/abc.py", line 1, in LibreOffice version 6.1.3.2-lp150.2.6.2.x86_64.įatal Python error: init_sys_streams: can't initialize sys standard streamsįile "/usr/lib64/python3.8/io.py", line 52, in įile "/home/scarabeus/abc.py", line 1, in Standard KDE Desktop-Installation 圆4 with all updates till 19th of November 2018 applied. On kubuntu the libreoffice works also without issues. The TDF-packages are working without issues. The investigations have shown, that the crash of libreoffice is only possible with the version from opensuse repository. It was closed as not an libreoffice bug (packaging bug).
I've already reported the bug in the LibreOffice Bugtracking system ( ). If you rename a abc.py file into abc.py.bck, libreoffice starts normally. start libreoffice and try to open existing or to create new empty writer file (possibly some of libreoffice file). place file abc.py in the home directory of the current user, containing something like "hello.world()"Ģ.
0 kommentar(er)
