文章摘要其实很多用户在运行软件或游戏的时候就出现过这种问题,如果是第一次遇见有的用户会可能认为软件出错了,其实并不是这样。其主要原因就是你电脑系统中某些进程、注册表、服务存在异常或没有安装一些系统运行库所导致的。 17.9k+1 其实很多用户在运行软件或游戏的时候就出现过这种问题,如果是第一次遇见有的用户...
Yes, this looks likehttps://cgit.freedesktop.org/libreoffice/core/commit/?id=327153471ae38abe90463f6272e00aaa996c5ba3and thushttps://bugs.documentfoundation.org/show_bug.cgi?id=121384(which is filed for writer and not calc, but...) > P.S. Yeah, LibreOffice doesn't touch encodings.py. ...
However, I can still reproduce this on 6.1.5, and changing absolutely nothing in the environment, including deletion of ~/.config/libreoffice does not seem to stop it, and there is no PYTHONPATH set in any form. I also noticed that pyuno/source/loader/pyuno_loader.cxx from the buster sou...
23:15 < _rene_> (and probably backport the upstream fix to buster. *sigh*) 23:16 < _rene_> yeah, libreoffice-lightproof-* is python. but I have libreoffice-lightproof-en installed, too 23:16 < bunk> libreoffice-lightproof-en makes it reproducible for me on buster 23:17 < _rene_...
> When opening any CSV file with LibreOffice Calc, Calc opens and executes > encodings.py from the current working directory. Demonstrably wrong, see below. > That presumably happens because > > Some file managers, including Krusader and mc, would launch localc in the ...
> When opening any CSV file with LibreOffice Calc, Calc opens and executes > encodings.py from the current working directory. That presumably happens > because There also is no mention of any "encodings.py" in anything in LibreOffice itself: ...
and subject line Bug#984703: fixed in libreoffice 1:6.1.5-3+deb10u7 has caused the Debian Bug report #984703, regarding libreoffice-calc: LibreOffice Calc executes code from current dir (encodings.py) when opening a .csv to be marked as done. ...