Bug 61649 - PRINTING: Printing Selected Frame doesn't print frame contents
Summary: PRINTING: Printing Selected Frame doesn't print frame contents
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: low minor
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks: Print
  Show dependency treegraph
 
Reported: 2013-03-01 04:36 UTC by Matt Needles
Modified: 2023-05-28 03:17 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Sample Document that may be used to demonstrate problem (143.92 KB, application/vnd.oasis.opendocument.text)
2013-03-01 04:36 UTC, Matt Needles
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Needles 2013-03-01 04:36:26 UTC
Created attachment 75724 [details]
Sample Document that may be used to demonstrate problem

LibreOffice 3.5.4.2 
Build ID: 350m1(Build:2)

Problem description: Selecting a (text) frame and printing with Selection option checked gives blank output.

Steps to reproduce:
1. Create a Labels document, with the page filled with synchronized labels
2. Fill the first (master) frame with text and some graphics (anchored to paragraphs in the frame.
3. Synchronize the labels.
4. Select the first frame and click the Print Direct icon from the toolbar
5. When the dialog appears, choose Selection.
Current behavior:
The output is blank.
Expected behavior:
A reproduction of the selected frame with all its contents
        
Operating System: Ubuntu
Version: 3.5.4 release
Comment 1 A (Andy) 2013-04-09 20:01:14 UTC
not reproducible with LO 4.0.2.2 (Win7 Home, 64bit)

@Matt: Does this issue still persist for you with the latest release of LO?
Comment 2 Joel Madero 2013-10-07 02:58:09 UTC
Thank you for reporting this issue! I have been able to confirm the issue on:
Version 4.1.1.2 
Platform: Ubuntu 13.04 x64
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 
As I've been able to confirm this problem on an earlier release I am changing the version number as version is the earliest version that we can confirm the bug, we use comments to say that the bug exists in newer versions as well.

Marking as:

New (confirmed)
Minor - doesn't prevent high quality work (as far as I can tell)
Low - default, seems appropriate

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 
LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link:
https://wiki.documentfoundation.org/QA/BugTriage

There are also other ways to get involved including with marketing, UX, documentation, and of course developing -  http://www.libreoffice.org/get-help/mailing-lists/. 

Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
Comment 3 QA Administrators 2015-04-01 14:40:00 UTC Comment hidden (obsolete)
Comment 4 Buovjaga 2015-04-19 14:05:27 UTC
Confirmed with attachment 75724 [details].

Win 7 Pro 64-bit Version: 5.0.0.0.alpha0+ (x64)
Build ID: 211c12b9c64facd1c12f637a5229bd6a6feb032a
TinderBox: Win-x86_64@42, Branch:master, Time: 2015-04-18_01:51:17
Locale: fi_FI

Ubuntu 14.10 64-bit
LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4
Comment 5 QA Administrators 2016-09-20 09:31:54 UTC Comment hidden (obsolete)
Comment 6 Thomas Lendo 2018-11-01 21:06:15 UTC
Still reproducible.

Version: 6.2.0.0.alpha1+
Build-ID: e33424dd887cb1a11a3dba2513ef0f4bf93a6dbe
CPU-Threads: 4; BS: Linux 4.15; UI-Render: Standard; VCL: gtk3; 
Gebietsschema: de-DE (de_DE.UTF-8); Calc: threaded
from today
Comment 7 QA Administrators 2019-11-02 03:45:40 UTC Comment hidden (obsolete)
Comment 8 Timur 2019-12-04 15:27:35 UTC Comment hidden (obsolete)
Comment 9 Timur 2021-05-27 10:24:10 UTC
Repro LO 7.2+ with attachment 75724 [details].
Comment 10 QA Administrators 2023-05-28 03:17:40 UTC
Dear Matt Needles,

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