Created attachment 111578 [details] Packes for reproducing the bug. Contains 3 images, a writerdocument an screenshot. Download the attaches Zip-file. Unzip the file. There are 3 screenshot, a Writer-document and a screenshot,which will show the problem. 1. Open LO, create a new Writer-document 2. Insert → Image → From File : "1.png" 3. Mark the image, set Anchor → AS Character 4. Insert → Image → From File : "2.png" 5. Mark the image, set Anchor → AS Character 6. Insert → Image → From File : "3.png" At this moment the buggy behavior happens: "2.png" seems to be gone. You could see a grey frame at the bottom of the writer page. Click somewhere in the document and the frame has gone. You could only see there must be another image in the document if you open the naviagtor. There you could see image1, image3 and image2 - right in this order, not image1, image2 and image3. Mark image2 and you will see there must be an image. Only this is a way to get it back. No great problems with only 3 images, but when I'm writing the Base-Handbook with over 100 images I don't know the number I must search for ...
Created attachment 111580 [details] Screenshot, which shows image in navigator, but not in writer Have a look at the screenshot. Image is marked in the navigator. The image seems to be gone outside the page. This bug happens since LO 3.5, last working version here LO 3.4.6.2, first version with buggy behavior LO 3.5.0beta0. The character of the bug differs a little bit. Up to LO 4.1 the third image appears at the bottom of the page and the second image seems to be lost. Since LO 4.2 the third image appears at the position the second image has been before. The bug appears also in all LO 4.3 and LO 4.4.0.1 Tested with OpenSUSE 12.3 64bit rpm Linux.
Seems the description isn't exactly enough. So let me try again: Download the attaches Zip-file. Unzip the file. There are 3 screenshot, a Writer-document and a screenshot, which will show the problem. 1. Open LO, create a new Writer-document 2. Insert → Image → From File : "p1.png" 3. Mark the image, set Anchor → AS Character 4. Put the cursor after the image and press [Enter] 5. Insert → Image → From File : "p2.png" 6. Mark the image, set Anchor → AS Character 7. Put the cursor after the image and press [Enter] 8. Insert → Image → From File : "p3.png" The second image will disappear. It will only happen when you insert the images in the order I described. Other way there is enough place for all images beneath each other. So don't change "p1.png" with "p2.png" or something else. You could see the second image isn't lost, when you open the naviagor. or just klick with the mouse at the bottom of the page. You will see the marks of the imageframe. Now search a little bit with the mouse. The cursor will show the image will be at the bottom border of the page, only ca. 2mm inside the writing-border of the first page of the document. You could see the result also by opening the Writer-document of the Zip-file.
confirmed with LibO 4.3.1.2 de Linux RPM x64 (parallel install) -> NEW
also reproducible with LibO 4.3.5.2 de Linux RPM x64, parallel install
Created attachment 111639 [details] Zip-file with Writer-document and one image. Put cursor at the end and add image ... Seems the description is too complicated. So I added another attachment. It contains a Writer-document and one image ("p3.png"). 1. Open wirter document. 2. Set the cursor at the end of the text on the page. 3. Insert → Image → From File : "3.png" The second image in the Writer-document will be lost. You could see the frame at the bottom of the document when using the navigator. The frame seems to be empty. A click on the frame and you could see in the properties of the image there should be the image inside the frame ...
also reproducable with LibreOffice 4.2.8 on Windows Vista (32-bit)
** 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 (5.0.4 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: 2016-01-17
Bug still exists with LO 5.1.0.2, OpenSUSE 42.1 Leap, 64bit rpm Linux.
Adding keyword 'bibisectRequest' to see whether this regression is already present in the oldest build of bibisect-43all repository or not. In case it's already present, change 'bibisectRequest' to 'preBibisect'. Otherwise, change 'bibisectRequest' to 'bibisected' and add a comment with the output from 'git bisect log'
(In reply to Xisco Faulí from comment #9) > Adding keyword 'bibisectRequest' to see whether this regression is already > present in the oldest build of bibisect-43all repository or not. > In case it's already present, change 'bibisectRequest' to 'preBibisect'. > Otherwise, change 'bibisectRequest' to 'bibisected' and add a comment with > the output from 'git bisect log' The first commit in bibisect-43all is from 2011-08-22 while 3.5.0 beta0 is from Nov-Dec 2011: https://wiki.documentfoundation.org/ReleasePlan/3.5 Thus changing to preBibisect Still repro. Arch Linux 64-bit Version: 6.1.0.0.alpha1+ Build ID: 5956828c88501ef1366e60010b05053a8e1e642e CPU threads: 8; OS: Linux 4.16; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on May 23rd 2018
Dear robert, 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
Have tested again with description in comment 2. Buggy behaviour is the same. Second image has been hidden at the bottom of the page. Tested with OpenSUSE 15, LO 6.2.4.2 64bit rpm Linux
Created attachment 158523 [details] Hidden image with Writer but no hidden with Ms Word or Google docs Bug unsolved with LibreOffice Writer 6.3.5.2 Patch : Open a new file Copy paste all to the new file. The hidden images are not copied to the new file.
1 Open a .doc file containing 2 images 2 delete these 2 images 3 insert a new image 4 save the file to .doc and to .odt 5 open .odt with writer: only one image is shown 6 Open .doc file with either MS Word or Google docs the 3 images are shown 7 rename .odt file to .zip 8 Extract the .zip file, in Pictures sub-directory all 3 files are present. Content of Manifest.xml under META-INF: <manifest:file-entry manifest:full-path="Pictures/10000000000002F3000000F249AFED37C5F7CF15.jpg" manifest:media-type="image/jpeg"/> <manifest:file-entry manifest:full-path="Pictures/100002010000077F000003914CEC0053F7C16880.png" manifest:media-type="image/png"/> <manifest:file-entry manifest:full-path="Pictures/10000000000003E3000002A9D61BA6E419043E8D.jpg" manifest:media-type="image/jpeg"/> 9 rename .zip back to .odt.
*** Bug 131884 has been marked as a duplicate of this bug. ***
reproduced as in comment 5 with: Version: 7.3.0.0.beta1 / LibreOffice Community Build ID: 436f14c25ec1847646b953cf13d0db4f7ca3be57 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
Reproduced as in comment 5 Version: 7.3.4.2 (x64) / LibreOffice Community Build ID: 728fec16bd5f605073805c3c9e7c4212a0120dc5 CPU threads: 2; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: CL Thanks for listening