Description: This command from cli causes the program to go into an infinite loop "/opt/libreoffice5.4/program/soffice --norestore --nodefault --convert-to pdf convert_buster_ok.docx" Actual Results: CPU 100%, never returns Expected Results: return in less that 10 sec with converted PDF file Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0
Created attachment 137265 [details] bad file
Created attachment 137266 [details] same file with image "wrap text" set to "inline"
This breaks the program "/opt/libreoffice5.4/program/soffice --norestore --nodefault --convert-to pdf convert_buster.docx" Same file - with small modification works "/opt/libreoffice5.4/program/soffice --norestore --nodefault --convert-to pdf convert_buster_ok.docx"
Confirmed in Version: 6.0.0.0.alpha1+ Build ID: 43d6b11a5c1dda0cc2c1e06c768eece25051a56c CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group - Version: 5.2.0.0.alpha1+ Build ID: 5b168b3fa568e48e795234dc5fa454bf24c9805e CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; Locale: ca-ES (ca_ES.UTF-8) - Version: 5.0.0.0.alpha1+ Build ID: 0db96caf0fcce09b87621c11b584a6d81cc7df86 Locale: ca-ES (ca_ES.UTF-8) - Version: 4.3.0.0.alpha1+ Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e - Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
Created attachment 137308 [details] GDB trace Trace was requested, I hope this has something useful.. I just Ctrl-C'd out of the looping. Arch Linux 64-bit, KDE Plasma 5 Version: 6.0.0.0.alpha1+ Build ID: 02a3abcceeb9be7f101b0bcaf55accc7fb6bfcf7 CPU threads: 8; OS: Linux 4.13; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on October 26th 2017
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Created attachment 150913 [details] bt with debug symbols On pc Debian x86-64 with master sources updated today, I could reproduce this.
Looks like a wrong report, not clear what was confirmed. Because bad file opens wrong 9 pages and hangs with LO 6.3 in Windows. Opens 6 pages and exports PDF in LO 7.1+. Even if someone uses --headless or --convert-to , he should test GUI open and save. I dislike seeing Blocks for bug 103266, bug 103378 which misses the point of the bug.
Bibisect 7.1: commit c391d02248a86bfc4a57448859eaf70403a365a7 Author: Jenkins Build User <tdf@pollux.tdf> Date: Fri Aug 28 20:44:04 2020 +0200 source d336e6c26012255015d3fc0caf8e7fafe14bd8f2 previous source faa36a5310f432a245baa8e9f765e759ab1cba2d Author Daniel Arato (NISZ) <arato.daniel@nisz.hu> 2020-08-24 11:05:17 +0200 committer László Németh <nemeth@numbertext.org> 2020-08-28 13:13:58 +0200 commit d336e6c26012255015d3fc0caf8e7fafe14bd8f2 (patch) tree 66fd21b95bd80520f8251f30620109f782703605 parent faa36a5310f432a245baa8e9f765e759ab1cba2d (diff) tdf#69647 sw layout: fix line spacing with inline pictures So I set Fixed.
attachment 137265 [details] is 5 pages in MSO, strange 2nd page, 2 frames aside that are different if resaved in MSO. Not for another bug, LO with 6 pages is OK.
The issue is still reproducible in Version: 7.1.0.0.alpha0+ Build ID: ff5ca4e5fc6a9fb24b0eb6eb629210b024473f67 CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded with command: time instdir/program/soffice --headless --convert-to pdf /home/xisco/Downloads/convert_buster.docx --outdir /home/xisco/Downloads/ I killed LibreOffice after real 42m37,549s user 0m0,142s sys 0m0,044s
Right, I missed to check original issue. Also seen with GUI, Linux only.
Created attachment 166159 [details] GDB trace 2020 in LO 7.1+ I tried with ./soffice --backtrace but LO crashed on opening file. Here is trace.
Confirmed in Version: 7.4.0.0.alpha0+ Build ID: e970bc67e4967c8d75db1d571283c6b489b080ce CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: en-IN (en_IN); UI: en-US Calc: threaded
Dear jodell, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug