Created attachment 168495 [details] ODT source file. libreoffice --headless --convert-to pdf --outdir . file.odt ...will generate file.pdf which will not visually match file.odt. However, if from LibreOffice GUI one uses File -> Export As -> Export Directly as PDF, the generated output file is ok. I expect the same output on the command line than in the GUI. The file contains an embedded Calc spreadsheet which is the source of the problem. If it is removed, the output is the same. It used to work very well a year ago. Version: 7.0.4.2 Build ID: 00(Build:2) CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-CA (en_CA.UTF-8); UI: en-US Ubuntu package version: 1:7.0.4_rc2-0ubuntu0.20.04.2 Calc: threaded
Created attachment 168496 [details] PDF file generated from CLI and for which the formatting is wrong.
Created attachment 168497 [details] PDF file generated from GUI and for which the formatting is right.
Clarification: 'If it is removed, the output is the same.' ..should have been written as: 'If (the Calc spreadsheet) it is removed, the output is then faithful to the ODT file.'
Still occurring in: Version: 7.1.1.2 / LibreOffice Community Build ID: 10(Build:2) CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-CA (en_CA.UTF-8); UI: en-US Ubuntu package version: 1:7.1.1~rc2-0ubuntu0.20.04.1~lo1 Calc: threaded
This is clear report but I couldn't reproduce with LO 7.0.4.2 in GTK3. Since I have no other advice, please try with profile reset/delete/rename.
Timur, you are right. I have reset my LibreOffice profile and now it works! I wonder what in the profile could possibly cause this bug to occur. Another bug I guess? But this bug probably does not happen to enough users to warrant efforts to fix it; there are so many more important things to work on LibreOffice, and the workaround / fix listed here is good enough. I am marking this issue as RESOLVED / WORKSFORME. This is how I have performed my LibreOffice profile reset: mv ~/.config/libreoffice/4/user ~/.config/libreoffice/4/user-old
Hans, it could be interesting what piece of the profile causes this. If you have the time, it could be worth bisecting registrymodifications.xcu in your profile. Ie. make a backup copy of the config file, then remove half of it, see whether the bug occurs, choose the half that remained or that was cut based on the result, and keep repeating until you're down to a single line, or a sufficiently small subset of lines. Alternatively, you could share the file, however better make sure there is no personal information in it in that case.
Created attachment 170762 [details] Cleaned file, all personal data removed; lines missing though. As suggested by Aron Budea, this is my registrymodifications.xcu (thus why it has '-cleaned' in its name, but will all the lines containing personal data removed. Because the lines have been removed, it might be that the file is inconsistent and does not work; I have not tried it. I do not have the time (unfortunately) to debug the problem. Maybe someone can take a jab at it.
Thanks! I gave it a quick try, but the exported PDF looked as expected to me. Oh well, it was worth a try.