Created attachment 136798 [details] sample it seems if the 'as character' image doesn't fit on the page it's not displayed. Steps to reproduce: 1. Open attached image 2. Delete the paragraph with X ( leave the image on the right ) Observed behaviour: Image on page 2 disappears. Not reproducible if the image on the right on page 1 is not present. Kind of corner case Reproduced in Version: 6.0.0.0.alpha0+ Build ID: 34f4446b0a5e04465216ff4ec2547aa82e0f06c2 CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk2; Locale: ca-ES (ca_ES.UTF-8); Calc: group
Regression introduced by: author Bjoern Michaelsen <bjoern.michaelsen@canonical.com> 2014-03-15 15:25:41 (GMT) committer Björn Michaelsen <bjoern.michaelsen@canonical.com> 2014-03-17 10:01:32 (GMT) commit 72a4987434368bfb0b15f5ebb70a52108d349d5f (patch) tree f5767ba202a9b89487b79aa66f055d727549f56b parent 5dc13b2d68eb30417f706935016d8bf7182b4aaa (diff) fdo#47355: partially revert c5a8a2c3cbcee0175127a0662e3d820ea4deea22 - that commit claimed to fix i#84870 - however that example document _still_ loops for me on current master even with the change - this caused the fdo#47355 regression in addition - thus reverting to heal fdo#47355, expecting i#84870 unchanged as broken before and in need of a proper fix Bisected with bibisect-43max Adding Cc: to Bjoern Michaelsen My commit: author Xisco Fauli <anistenis@gmail.com> 2017-06-12 16:05:27 (GMT) committer Xisco Faulí <xiscofauli@libreoffice.org> 2017-06-14 08:41:03 (GMT) commit 3919d87210ea12ed3166c649ac52730026db01a4 (patch) tree 552866f9e5f369e404ec2b2a04a112ae55fc1c8f parent e07492e14790262abc24d44c280bd71e5ebeddf4 (diff) tdf#104640, tdf#108469: Insert image where the cursor is Partially revert 72a4987434368bfb0b15f5ebb70a52 Besides, add bDelta to the condition so the statement is false if the image is resized Doesn't fix this issue. Note: if !bDelta is removed from https://opengrok.libreoffice.org/xref/core/sw/source/core/text/frmform.cxx#1087 the issue is not reproducible, however, bug 47355 is reproducible again
** 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
Bug still exists on LO 6.4.3.1 with OpenSUSE 15.1 64bit rpm Linux
repro 7.2+
Dear Xisco Faulí, 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