Hi,
Am 13. November 2024 01:25:35 MEZ schrieb Vincent Lefevre <vinc...@vinc17.net>:
>On 2024-11-12 20:28:49 +0100, Rene Engelhard wrote:
>> Am 12.11.24 um 17:08 schrieb Vincent Lefevre:
>> > When I run the libreoffice command while a soffice.bin process is
>> so basically starting to try a new soffice.bin
>> > running (e.g. as a consequence of bug 1087368), LibreOffice does not
>> > start: the command just returns without any error.
>>
>> So what? A LibreOffice is running, so... If you had a libreoffice
>> running as a daemon listening to connctions that is the same
>>
>> This works as designed, afaik.
>
>No, it does *not* behave as documented. See the "libreoffice --help"
>output.
>
>"Using without special arguments:
>Opens the start center, if it is used without any arguments."
>
>Other usages such as providing a file argument or using --writer to
>create an empty Writer document have no effect either, while a window
>should have been opened.
All that implies a not yet running LO.
>The fact that LibreOffice is already running in the background is just
>internals. It still needs to behave as documented and in a useful way.
>With the current status, there is no way to open a LibreOffice window.
Kill the stray soffice.bin?
It is all over the net that you can't do GUI and soffice.bin
listening/daemon/headless/whatever at the same time.
That is touching fundamentals LO upstream will definitely not change as long as
this "issue" already exists...
Regards
René
