Bug 118379 - One Page will not be Printed if Pages are Separated with Manual Page Breaks
Summary: One Page will not be Printed if Pages are Separated with Manual Page Breaks
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Print Print-Preview
  Show dependency treegraph
 
Reported: 2018-06-25 19:37 UTC by Harald Koester
Modified: 2025-11-01 03:12 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Example document. (9.38 KB, application/vnd.oasis.opendocument.text)
2018-06-25 19:37 UTC, Harald Koester
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Harald Koester 2018-06-25 19:37:11 UTC
Created attachment 143111 [details]
Example document.

I order to reproduce:

[1] Open attached document.
[2] Select the content of page 2 and page 3.
[3] Print selected pages:
(a) Menu: File > Print > General > Selection. Preview: Only one page is selectable. The content of page 2 and 3 (“2” and “3”) are merged together on one page. Expected: 2 pages with different content should be selectable.
(b) Click OK: Only one page with wrong content is printed. Expected: Print of 2 pages with correct content.

Tested with version 6.0.5 (64 bit, Win 10).

The same problem exists if you export the selected pages to a pdf document. 
Bug already exists in version 3.3.0. Hence inherited from OOo.
Comment 1 Susan Gessing 2018-06-25 20:57:01 UTC
I was able to reproduce this bug in Windows 8.1 in the following:

Version: 6.0.5.2 (x64)
Build ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16
CPU threads: 4; OS: Windows 6.3; UI render: GL; 
Locale: en-US (en_US); Calc: CL

and

Version: 6.2.0.0.alpha0+
Build ID: b1740fba0d1e6e3d69c3781734509317f42a0e4f
CPU threads: 4; OS: Windows 6.3; UI render: GL; 
TinderBox: Win-x86@42, Branch:master, Time: 2018-06-15_08:49:04
Locale: en-US (en_US); Calc: CL
Comment 2 QA Administrators 2019-06-26 02:45:41 UTC Comment hidden (obsolete)
Comment 3 Harald Koester 2019-06-28 08:02:58 UTC
Bug still exists in version 6.2.4 (64 bit) with Win10.
Comment 4 QA Administrators 2021-06-28 03:48:03 UTC Comment hidden (obsolete)
Comment 5 BogdanB 2022-01-27 21:49:46 UTC
The bug still here

Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: 2f4f4cbeb8e50081d607b86b0475b93971c40ab8
CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded
Comment 6 QA Administrators 2025-11-01 03:12:15 UTC
Dear Harald Koester,

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