Problem description: Steps to reproduce: 1. create a bulk letter (with Calc database) 2. print it 3. get 2 pages instead of one. The second one is empty Current behavior: bulk letter has two pages instead of one. Second one is empty. My letter has 13 recipients but the printer produces 25 pages instead of 13. Expected behavior: bulk letter should have only one printed page Platform (if different from the browser): Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20100101 Firefox/11.0
Please provide the bulk letter with calc database so that we can triage based on what you are creating and seeing the bug in. Marking as NEEDINFO, once the attachments are made please reopen as UNCONFIRMED. Thank you
Created attachment 67242 [details] contains a database and a bulk letter and a print result created with pdf creator The bug was not reproduceable with an epson stylus DX4200 printer, but with PDF-Creator and Brother MFC-235C
(In reply to comment #2) > The bug was not reproduceable with an epson stylus DX4200 printer, but with > PDF-Creator and Brother MFC-235C Checked with: LO 3.6.3.1 Build ID: f8fce0b Windows XP Professional SP3 Could not reproduce. Letters printed to PDF as expected - no blank pages (File>Print>Yes>Output File>Save as single document>PDF). Haven't checked with real printer.
reproduced in 3.6.3 on RFR 17 64 bit and in 3.4.2 on Windows XP 32 bit File>Print>Yes> _OK_ now appears dialog "Print". On preview on left side of it we can see that present 3 pages for printing, second is empty.
Reproduced in LO 3.6.4, Windows 7 Pro On a 1-page mail merge, a page break is inserted at the end of the page in the merged doucment. The result is an empty page added at the end of the 1-page document. Makes mail merge very hard or unusable is the number or records is high (100's or 1000's). Terrible waste of emply/blank pages.
I went further on this issue and it may be working as designed, and extra care from user is needed. The sample I have has one page and the last paragraph is at the bottom of the page. So a mail-merge page break is added after an automatic page break, generating an extra blank page. I supressed one line in the form letter, to avoid the last paragraph to touch the bottom of the page and the extra blank page vanished. This may be flagged as WORKSFORME, but it is a weird behaviour for the uneducated user.
Adding self to CC if not already on
** 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.0.4 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: 2016-01-17
Dear Klocke, 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
This Bug still exists and can be reproduced. I attached some screenshots (not the real document and database, as the database-links are relative and did not work when moving to another location). Libreoffice 6.4.1.2 on Windows 10, all patched: Creating a form letter / mail merge / bulk letter / Serienbrief and saving it to a file or printing inserts on all even page an empty page. In the sample attached we have 3 database entries, which should result in three pages, but mail merge generates 5 pages. As there are many help-requests and workarounds on other websites, I suggest to prioritize this issue. https://de.openoffice.info/viewtopic.php?t=8058 https://listarchives.libreoffice.org/de/users/msg00812.html Thank you!
Created attachment 159012 [details] Sample Document
Created attachment 159014 [details] Sample Database
Created attachment 159016 [details] Sample Result, see the page numbers, even pages are not visible
Created attachment 159043 [details] Sample ODT I reattach single files, because it's wrong practice to zip them.
Created attachment 159044 [details] Sample ODS
Created attachment 159045 [details] Sample as printed from reporter
Repro 7.0+. Reason is page break in Writer that adds blank page all the way from OO. So if we print to file, we can see that n records makes n real pages, but Writer shows 2n-1 pages, counting also blanks. Can be avoided while in Print dialog with turning off Writer-Print auto inserted blank pages. Funny that I close as NotABug after 8 years..but that's how it is. I don't know why that option is on by default. But that's not only in Mail merge but always. Could be discussed somewhere else, whoever is interested please search both open and closed bugs.
Created attachment 159050 [details] Sample print merge saved in single ODT
Option can be turned off in Options-Writer-Print. I don't know why it's default is to be on.
*** Bug 134723 has been marked as a duplicate of this bug. ***