Created attachment 66643 [details] Two pages on one
Please explain step by step what you did to encounter this problem. End attach the original OpenDocument file. Best regards. JBF
hi Jean-Baptiste Faure 1. problem.docx it's original file from my bank. 2. in LO 3.6.2.1 RC1 I see only one page, but there should be two. http://floomby.ru/s1/2EcG7 - screenshot Sorry for my English.
FILEOPEN RTF: page breaks in otherwise empty paragraphs ignored https://bugs.freedesktop.org/show_bug.cgi?id=48440 This bug is FILEOPEN DOCX: page breaks in otherwise empty paragraphs ignored
Problem the same problem in rtf the file of a bug closed above. Thanks!
LibreOffice 4.1.0 beta2 (2013-06-08) =(
the bug is not fixed in libreoffice-4-1~2013-07-26_22.16.17_LibreOfficeDev_4.1.1.0.0_Win_x86.msi and master~2013-07-27_22.47.00_LibreOfficeDev_4.2.0.0.alpha0_Win_x86.msi
up(
Created attachment 90691 [details] After opening file in LibreOffice
Created attachment 90692 [details] Comparison between Original File and Roundtrip File
After Opening file in LibreOffice it shows one page file instead of 2 page file.
** 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 on a currently supported version of LibreOffice (4.4.1 or later) https://www.libreoffice.org/download/ *If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior *If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18
LibreOffice 4.4.3 RC1 - the bug isn't fixed. Win_x86 After Opening file in LibreOffice it shows one page file instead of 2 page file.
** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Still reproducible with LO 5.2.3.0+ and current master under Ubuntu 16.04 x86-64. Best regards. JBF
** 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
So, this table-looking document is composed of lines and tiny textbox frames. Not surprising that no one has looked at it, and probably never will.
The document is no longer displayed in 1 page but in 2 in Version: 6.4.0.0.alpha0+ Build ID: ea19b0c0230fcc730245ecd445c03164cb6a1d18 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded I think we can close this as RESOLVED WORKSFORME
Also fixed in Version: 6.3.0.0.beta2+ Build ID: e17e30dceb110e780a7e7e89c2ede854d4bc38a7 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded
(In reply to Xisco Faulí from comment #17) > The document is no longer displayed in 1 page but in 2 in Based on bibisect-linux-x64-6.3, this occurred with the range: bibisect commit 375eecab87e6e966ed7ac140cfbb49844ca5e494 Author: Jenkins Build User <tdf@pollux.tdf> Date: Tue Apr 30 16:32:52 2019 +0200 source bf8c8699f7ed09519db2041e1ec1554097e94ab4 source bf8c8699f7ed09519db2041e1ec1554097e94ab4 source 5879351aeb1935e2bf86fda59703f7d49fdeb6ed source 3d37463eec0c891243a8971a34903b2da01c9e24 source 31ae7509003b1e650463ee1468c0b315ba13efe6 source f6f53f76e15f5eecc5b6ce56e471c53cebfea8ad source cc899c6967238877f0094bcf00627145e484ffec source b593634d3cfbb2fc8522d99ce1c3f2a11445ea59 likely with commit f6f53f76e15f5eecc5b6ce56e471c53cebfea8ad Author: Justin Luth on Wed Apr 24 22:20:51 2019 +0300 tdf#123636 writerfilter: handle deferred breaks on frames