Bug 34191 - Empty pages print when doing a circular letter
Summary: Empty pages print when doing a circular letter
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
3.3.0 release
Hardware: x86 (IA32) All
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2011-02-11 11:45 UTC by Joachim Manke
Modified: 2011-02-12 06:19 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Joachim Manke 2011-02-11 11:45:33 UTC
I have created a circular letter of one page, linked it to a BASE database and wanted to print all 29 letters. After formatting Libre Office told me, that it is going to print 57 pages. Checking this I found out, that there was an empty page after all letters exept the first one.
Comment 1 Rainer Bielefeld Retired 2011-02-12 00:51:00 UTC
I believe that's because you have selected that behavior in your settings?

May I ask you to read hints on <http://wiki.documentfoundation.org/BugReport> carefully?
Then please:
- Attach screenshots with comments (you can add information using LibO DRAW
  and then attach your screenshot with comments as PDF) 
- Attach a sample document 
- Contribute a step by step instruction containing every key press and every 
  mouse click how to reproduce your problem (did you use Mail merge wizard or 
  menu 'File > Print > ...'?
- add information 
  -- concerning your settings in 'Tools > Options > Writer > Pringt - Other'
  -- concerning your OS 
  -- concerning your LibO localization
  -- everything else crossing your mind after you read a.m. URL
Comment 2 Joachim Manke 2011-02-12 05:33:20 UTC
Sorry, you'r right. I found the reason in the general print setting of writer, where "Print automatically inserted empty pages" was ticked. So - no error!
Comment 3 Rainer Bielefeld Retired 2011-02-12 06:19:28 UTC
@Joachim Manke:
Thank you for your quick response.
Do you want to help? It would be kind if you could try to reproduce one of our UNCONRFIRMED Bug reports: