https://bugs.documentfoundation.org/show_bug.cgi?id=163863

--- Comment #11 from yarma22 <[email protected]> ---
>> soffice --headless > /dev/null

> not in background ?

>> kill "$pid"

> still ? 
> where is $pid defined/assigned ?

Sorry, these were typos when preparing my previous comment, since I simplified
my script to its essential components for the purpose of readability.

> please make sure to report accurately, since details matter.

You're right. Therefore, I re-created a script from scratch. I managed to
simplify it further. Please find it below with its actual output. Note that
`dir` contains 300 files.

odt2pdf.sh:
```
soffice --headless > /dev/null &
soffice --headless --convert-to pdf --outdir PDF dir/*.odt
```

```
$ bash odt2pdf.sh 
$ ls PDF/*.pdf | wc -l
248
$ 
```

However, if I start the background soffice interactively, it works, e.g.

odt2pdf.sh:
```
soffice --headless --convert-to pdf --outdir PDF dir/*.odt
```

```
$ soffice --headless > /dev/null &
[1] 45460
$ bash odt2pdf.sh 
Converting...
Done.
$ 
[1]+  Done                    soffice --headless > /dev/null
$ ls PDF/*.pdf | wc -l
300
$
```

Basically, it seems that when `soffice` is started in the background from a
script, the workaround you mentioned doesn't work.


> when launching "libreoffice", it actually calls :

> 836291  271955  0 18:24 pts/1    00:00:00 
> /usr/lib/libreoffice/program/oosplash --
> 836326  836291 17 18:24 pts/1    00:00:02 
> /usr/lib/libreoffice/program/soffice.bin
> ...
> whereas soffice.bin just gets it shortened : 
> usr/lib/libreoffice/program/soffice.bin--headless--convert-topdf--outdirPDF001.odt002.odt003.odt
>   [...] 247.odt248.odt

Nice catch! I updated my script to invoke
`/usr/lib/libreoffice/program/soffice.bin` directly instead of `soffice` and it
worked! It can now generate the PDF files for all the ODT files and :)))

Until the actual issue is fixed, that's definitely a super workaround. Thanks
so much for your help!

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to