Created attachment 123802 [details] sample ods file When I set the Flip to the image, it did not displayed in the print preview. Steps to reproduce: 1.Open new spreadsheet and insert an image. 2.Click [File] - [Print]. ---> Image is displayed. 3.Select image and right-click. 4.Select [Flip] - [Vertically] or [Horizontally] 5.Click [File] - [Print]. ---> Image is not displayed. In version 4.1.2, this issue does not occur. Expected behavior: Even when I set the Flip, I want to display image. OS: Windows7 Professional Version: 5.1.0.3 Build ID: 5e3e00a007d9b3b6efb6797a8b8e57b51ab1f737 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; Locale: ja-JP (ja_JP) Best regards.
I'll correct the previous description. Image did not display in "print preview". When I print, it was displayed.Flip setting also had been keep. (In the printing of the confirmation screen, the setting of the Flip does not keep) > 2.Click [File] - [Print]. 2.Click [File] - [Print preview].
You mean print preview Ctrl-Shift-O? I do not see the problem. 64-bit, KDE Plasma 5 Build ID: 5.1.1.3 Arch Linux build-2 CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; Locale: fi-FI (fi_FI.UTF-8)
I can confirm with 4.2.8.2, 5.1.13 and 5.2, win7
(In reply to Buovjaga from comment #2) > You mean print preview Ctrl-Shift-O? > I do not see the problem. > > 64-bit, KDE Plasma 5 > Build ID: 5.1.1.3 Arch Linux build-2 > CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; > Locale: fi-FI (fi_FI.UTF-8) Yes. [File] - [Print preview] or [Ctrl]+[Shift]+[O].
Changing OS field as this is Win-only.
reproducible with Version: 4.5.0.0.alpha0+
According to comment 3, it can be reproduced with 4.2.8.2. Updating version then.
Adding keyword 'preBisect' as this regression was introduced before branch 4.4 and therefore it can't be bibisected as there's no bibisect repository for this branch.
** 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! Warm Regards, QA Team MassPing-UntouchedBug
Still reproducible in Versión: 6.0.1.1 Id. de compilación: 60bfb1526849283ce2491346ed2aa51c465abfe6 Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; Configuración regional: es-ES (es_ES); Calc: group Zooming in and out the print preview shows some parts of the image...
Probably the root cause is the same as in bug 98482
Dear HD, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This is reproducible in Linux, and still occurs with LO 7.3.0.0.alpha0+ (36efb384a66b6dd645e0ae80fd7df68370a9dc8b). (In reply to Xisco Faulí from comment #11) > Probably the root cause is the same as in bug 98482 It is. Bibisecting with repo bibisect-42max revealed two relevant changes, after the first the image isn't shown in the Print dialog's preview, and after the second, the image is shown again, but not flipped. This second commit is likely responsible for the bug. First commit: https://cgit.freedesktop.org/libreoffice/core/commit/?id=e08407052f556c981e533f532815125769212685 author Armin Le Grand <alg@apache.org> 2013-01-15 08:19:38 +0000 committer Caolán McNamara <caolanm@redhat.com> 2013-06-13 15:56:09 +0100 "Resolves: #i121534# only handle bitmaps which are inside visible area" Secont commit: https://cgit.freedesktop.org/libreoffice/core/commit/?id=9bb96049addebd8907854730713d8a3f5f033e34 author Armin Le Grand <alg@apache.org> 2013-01-23 13:27:50 +0000 committer Caolán McNamara <caolanm@redhat.com> 2013-06-14 16:00:13 +0100 "Resolves: #i121534# Reintegrating changes for rotated bitmap support"
Dear HD, 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
(In reply to Aron Budea from comment #14) > This is reproducible in Linux, and still occurs with LO 7.3.0.0.alpha0+ > (36efb384a66b6dd645e0ae80fd7df68370a9dc8b). > > (In reply to Xisco Faulí from comment #11) > > Probably the root cause is the same as in bug 98482 > It is. Bibisecting with repo bibisect-42max revealed two relevant changes, > after the first the image isn't shown in the Print dialog's preview, and > after the second, the image is shown again, but not flipped. This second > commit is likely responsible for the bug. > > First commit: > https://cgit.freedesktop.org/libreoffice/core/commit/ > ?id=e08407052f556c981e533f532815125769212685 > author Armin Le Grand <alg@apache.org> 2013-01-15 08:19:38 +0000 > committer Caolán McNamara <caolanm@redhat.com> 2013-06-13 15:56:09 +0100 > > "Resolves: #i121534# only handle bitmaps which are inside visible area" > > Secont commit: > https://cgit.freedesktop.org/libreoffice/core/commit/ > ?id=9bb96049addebd8907854730713d8a3f5f033e34 > author Armin Le Grand <alg@apache.org> 2013-01-23 13:27:50 +0000 > committer Caolán McNamara <caolanm@redhat.com> 2013-06-14 16:00:13 +0100 > > "Resolves: #i121534# Reintegrating changes for rotated bitmap support" Adding CC to Armin
*** Bug 158951 has been marked as a duplicate of this bug. ***