Printing preview looks OK, Exporting as PDF looks OK, Sending to printer results in blank box on top of the page (also the small preview in the print window).
Tested with v22.214.171.124, v5.5.4, v6.0.1, same results.
Steps to Reproduce:
1. Please download test file from https://www.file-upload.net/download-12980655/test.ods.html
2. Open with Calc
3. Open print dialog, you will see a big blank box which overlays the content.
4. For comparison, please also try exporting to PDF which works fine.
Blank box is shown.
Content should be printed like it works fine with PDF export.
User Profile Reset: Yes
CPU-Threads: 4; Betriebssystem:Windows 6.2; UI-Render: Standard;
Gebietsschema: de-DE (de_DE); Calc: group
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
Created attachment 139929 [details]
test file where the blank box error appears
This is the test file.
It was converted from XLSX format (but same result with both formats).
Build ID: df72c65fdaf5f1276d1759ba3e7eec83eaaa2d20
CPU threads: 2; OS: Linux 4.14; UI render: default; VCL: kde4;
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:libreoffice-6-0, Time: 2018-02-15_02:20:53
Locale: nl-BE (en_US.UTF-8); Calc: group
also with master
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
** 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 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!
Repro 6.3+ in Win. Repro 4.1 no 4.0. Seems regression.
Using 41max I get this (but not sure what it means):
dadd589cd0633db4e126f0a6ab2907ffeef34563 is the first bad commit
Author: Matthew Francis <firstname.lastname@example.org>
Date: Fri Sep 18 10:13:10 2015 +0800
Bibisect: This commit covers the following source commit(s) which failed to build
Author: Michael Meeks <email@example.com>
AuthorDate: Mon Dec 17 19:55:32 2012 +0000
Commit: Michael Meeks <firstname.lastname@example.org>
CommitDate: Mon Dec 17 19:57:54 2012 +0000
fdo#58399 - revert attempts to untangle and accelerate this mess.
The bug has a great series of linked bugs and stack-traces; the
weakref / mixed tools & UNO lifecycle here is simply hideous.
:040000 040000 99f15e051caeacf933d5bb1f0749720ffa4131ca dd73dfa370efeb20fb22ef3f616d7256824e689a M opt
Apart from Michael's https://gerrit.libreoffice.org/plugins/gitiles/core/+/bb3f2900a867fdcb6df916fff58199b4ce94dd05 , these also look suspicious to me:
commit f828e91d1b2f0491e3d1c724ddd12f1b9177f466 [log]
author Noel Power <email@example.com> Mon Dec 17 17:49:00 2012 +0000
committer Noel Power <firstname.lastname@example.org> Mon Dec 17 17:49:00 2012 +0000
parent a108f4b14e119736c6a24f00cbfe87acb71e1e4a [diff]
fix problematic calc object selection after object create (at non 100% zoom)
sometimes difficult to select custom shapes etc. created at non 100% zoom
levels. workaround was to use selection tool to select an area.
commit 97b583a7bfb5dc9000290c3bdc8df8751a97d65d [log]
author Kohei Yoshida <email@example.com> Mon Dec 17 11:57:06 2012 -0500
committer Kohei Yoshida <firstname.lastname@example.org> Mon Dec 17 12:55:40 2012 -0500
parent f828e91d1b2f0491e3d1c724ddd12f1b9177f466 [diff]
Change the order of always, never, ask enumerations.
This tri-state option is commonly ordered ask-always-never or
always-never-ask, but not always-ask-never, which is not very common.