Bug 119764 - Shape set to be not printed in XLSX appears in Print dialog preview, and is printed
Summary: Shape set to be not printed in XLSX appears in Print dialog preview, and is p...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: All All
: low normal
Assignee: Not Assigned
Keywords: filter:xlsx
Depends on:
Blocks: Print XLSX-Shapes
  Show dependency treegraph
Reported: 2018-09-08 23:49 UTC by Aron Budea
Modified: 2023-05-12 03:19 UTC (History)
0 users

See Also:
Crash report or crash signature:

Sample XLSX (8.90 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2018-09-08 23:50 UTC, Aron Budea

Note You need to log in before you can comment on or make changes to this bug.
Description Aron Budea 2018-09-08 23:49:59 UTC
This is related to bug 108691, another combination of the visibility + printability setting: the shape is visible, but in its properties, 'Print object' is unchecked, thus it's not supposed to be printed.

Currently in Calc this property is ignored, because it's stored in a different place compared to the visibility setting. For some basic details, see bug 108691 comment 4.

I assume the setting isn't used often.

Observed using LO 6.2 master daily build (18-09-07), 3.3.0 / Windows 7.
Comment 1 Aron Budea 2018-09-08 23:50:36 UTC
Created attachment 144756 [details]
Sample XLSX
Comment 2 QA Administrators 2019-09-09 05:30:21 UTC Comment hidden (obsolete)
Comment 3 Timur 2019-09-10 12:36:46 UTC
I don't see that Calc has such property not to print an object.
Comment 4 Aron Budea 2019-09-10 13:07:51 UTC
It might not be in Calc, but it exists in ODF (which doesn't matter when it comes to handling an XLSX file, but means the spec was created with this in mind):

The bug is still there in (61b757f31f25cda6d595f64226181c7a82ce8d7f) / Ubuntu 19.04.
I guess the prio can be lowered, it's not a commonly used setting in MSO, either.
Comment 5 QA Administrators 2023-05-12 03:19:52 UTC
Dear Aron Budea,

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