On 28/08/2019 12:20, Jerry Geis wrote:
There's apparently another instance of soffice.bin already running (for
the same UserInstallation), so this one just passes its cmd line args
(none in this case) to the other instance and exits successfully.
Thank you - Where/how does it get this? I have --nolock on the command line,
--nolock has no influence on that.
the file show does not exist... /tmp/OSL_PIPE_0_SingleOfficeIPC_53bc4297d6d012e1a744f3977d159334
and ps ax | grep soffice does not show anything.
Then I'm clueless what's going wrong for you. That you had captured the
strace output of an uninteresting soffice.bin (started while another
soffice.bin was still running) was the most likely explanation for the
strace output you presented.
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.