https://bugs.documentfoundation.org/show_bug.cgi?id=157815
Bug ID: 157815
Summary: LibreOffice becomes an unkillable process after
loading a file with embedded fonts.
Product: LibreOffice
Version: 6.4.0.3 release
Hardware: x86-64 (AMD64)
OS: other
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: LibreOffice
Assignee: [email protected]
Reporter: [email protected]
This problem only seems to occur when LibreOffice is started from a service on
Windows Server 2016.
Steps to reproduce:
1. Create a new .odt file with embedded fonts by going to File -> Properties ->
checking "Embed fonts in the document"
2. Create a new .NET Windows service. (It might apply to non-.NET services as
well, I haven't tried)
3. In the OnStart() method of the service, start the LibreOffice process with
the "--convert-to pdf" argument and passing in the file path of the embedded
fonts document from step 1. I'm using .NET 4.6.1 and have included sample code
below.
Expected Result: LibreOffice converts the ODT file to a PDF file.
Actual Result: LibreOffice doesn't create the PDF file and hangs. Any attempts
to kill the process fail, even with admin rights.
Other Notes:
1. This bug was introduced with version 6.4.0.1. Version 6.3.6.2 works fine.
2. This also happens when trying to convert from .docx to .odt, so it doesn't
seem to be related to the file formats.
3. The code below works fine when run from a normal program (not a service), or
when run from a service on Windows Server 2019.
---------------------------------------------------
-- C# code in the Windows service OnStart() method
---------------------------------------------------
const string inputFilePath =
@"C:\Temp\FileConverterTest\Files_Input\TestEmbeddedFonts.odt";
const string outputFolderPath = @"C:\Temp\FileConverterTest\Files_Output";
ProcessStartInfo info = new ProcessStartInfo(
@"C:\Program Files\LibreOffice\program\soffice.exe",
"--convert-to pdf \"" + inputFilePath + "\" --outdir \"" +
outputFolderPath + "\"");
info.WindowStyle = ProcessWindowStyle.Hidden;
info.CreateNoWindow = false;
info.UseShellExecute = false;
Process.Start(info);
--
You are receiving this mail because:
You are the assignee for the bug.
