Created attachment 52495 [details] Sample document with displaced graphics How to reproduce: 1: Create a table in writer 2: Add lines in a cell until the cell spans two pages 3: Draw a graphics object on the second page of the cell, inside the cell 4: Set "Anchor to paragraph" or "Anchor to character" for the graphics object 5: Save the document, and then close it. 6: Reload the document Expected result: Graphics on original position Actual result: Graphic shifted to right page border Reproducible: always Observations: - Problem is present if "Anchor to page" is selected. - Problem is not present when the graphics are in the first part of the cell, before the page break. Tested versions: OpenOffice 3.1.0 on Windows XP OpenOffice 3.1.0 (portable) under wine on openSuSE 11.4 OpenOffice 3.3.0 on Windows XP LibreOffice 3.4.2 from OBS Stable on openSuSE 11.4 (64-bit) LibreOffice 3.4.3 (portable) under wine on openSuSE 11.4 (64-bit)
Correction: Problem is NOT present if "Anchor to page" is selected.
I can confirm this with LO 3.5 beta on Windows XP.
Created attachment 55984 [details] Test-case with Drawing Objects in a Cell on First and Second Page
Created attachment 55985 [details] Screenshot of Test-Case before closing
reproduced in 3.3.4 and 3.6.0 master on Fedora 64 bit
reproducible with LO 4.0.2.2 (Win7 Home, 64bit)
Reproducible on Ubuntu 12.04 (32-bit) with MASTER Version: 4.2.0.0.alpha0+ Build ID: c2530b02311c46529eed53ee688bf6c83ce4b86
Reproducible on Version 4.1.1.2
Reproducible in master on openSuSE 12.3 (64-bit) Version: 4.4.0.0.alpha0+ Build ID: 8b499cea76577b4221fccb17703aa9e86b625e90
** 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 on a currently supported version of LibreOffice (4.4.1 or later): https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-07-18
WITH A FRESH DOCUMENT I can't reproduce this problem any more. Tested on: Ubuntu 14.04 (64-bit) with Version: 4.2.8.2 Build ID: 420m0(Build:2) OpenSuSE 13.2 (64-bit) with Version: 4.4.4.3 Build ID: 40m0(Build:3) Locale: en_US.UTF-8 The attached test document is still broken. RESOLVED WORKSFORME?
(In reply to Stephan van den Akker from comment #11) > WITH A FRESH DOCUMENT I can't reproduce this problem any more. Tested on: Thanks for testing! > The attached test document is still broken. Confirmed in master 5.2.0 > RESOLVED WORKSFORME? Could do. What about the initial bug file? This means there is a difference between how anchoring (or whatever) was set in the time when the file was made.. Ignore that? Ciao - Cor
(In reply to Cor Nouws from comment #12) > Could do. What about the initial bug file? This means there is a difference > between how anchoring (or whatever) was set in the time when the file was > made.. Ignore that? or file e new bug, if needed ;)