Stephan Bergmann-2 wrote
How exactly do you launch LO? If by calling install/program/soffice.bin
instead of install/program/soffice then the behavior is expected
(soffice starts and controls soffice.bin, which needs to re-start on
first start after any upgrade to cater for potential changes in bundled
extensions etc.).
I followed the instructions here:
https://wiki.documentfoundation.org/QA/HowToBibisect
I typed:
./opt/program/soffice.bin
in the folder bibisect40
At first launch, I get this message:
Fontconfig warning:
"/home/olivier/Téléchargements/bibisect40/opt/share/fonts/truetype/fc_local.conf",
line 13: Having multiple <family> in <alias> isn't supported and may not
works as expected
The splash screen appears 1 second then disappears.
At the second launch, I get:
Fontconfig warning:
"/home/olivier/Téléchargements/bibisect40/opt/share/fonts/truetype/fc_local.conf",
line 13: Having multiple <family> in <alias> isn't supported and may not
works as expected
/home/olivier/Téléchargements/bibisect40/opt/program/pythonloader.py:60:
UnicodeWarning: Unicode equal comparison failed to convert both arguments to
Unicode - interpreting them as being unequal
if 1 == os.access( encfile( path ), os.F_OK) and not path in sys.path:
And LO starts.
Olivier
--
View this message in context:
http://nabble.documentfoundation.org/Grammar-checker-Undocumented-change-in-the-API-for-LO-4-tp4030639p4040599.html
Sent from the Dev mailing list archive at Nabble.com.
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.