Description: I don't know how to reproduced, but I'm really pissed off. Two days ago I created a document with 5 linked images. A very simple one, really. One image per page, png/jpg, and a small caption after it. Everything worked fine. Today I opened the document just to see that the first (house.jpg) and third (boris.png) images are missing. No, I don't mean that writer show me "image not found" placeholder. They simply missing. What the heck. I really want to use Writer over Word because it have table styles. But I simply cannot. Writer is actually pre-pre-alpha. How can I use software that will sinetly, like a Japanese shinobi, kill my data, harm my documents? This is the worst possible thing the software can do. Silently. Harm. User's. Files. I would be OK to pay $500 for S T A B L E Writer. But. If LO if so unstable, then maybe you should make a public announce that this is just pre-pre-pre-alpha and nobody should take it seriously unless the version 0.5 is ready? The problem is not just missing images. Few years ago there was a similar bug (now fixed) when Writer silently removed any formatting. That is, you will notice the missing formatting only when you open the document next time. Everybody blame Microsoft FUD (Fear, uncertainty, and doubt) "propaganda" about open-source software. I don't care what Microsoft says, but the bugs like the ones described above do exactly the same: they make me feel fear, uncertainty, and doubt. How can I trust the software after this? It's like one night you awaked and see your wife with a knife near your neck, and she crazy laught. It would be quite hard to trust her after this, right? Steps to Reproduce: - Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: -
Created attachment 177405 [details] contentxml
The file was ODT, not DOC or DOCX I included only the content.xml and not the document itself by intent. I don't want to share my template.
And the following bullshit is from LibreOffice Facebook official page: > Using the wrong office suite could cost you your job! Check > out this post from Twitter – someone is locked out of their > documents in Microsoft Office. This happens a lot. > > But this wouldn't happen with LibreOffice! Our software > respects your freedom and privacy, and doesn't lock you in. > Help us spread the word about our free office suite, used > by millions around the world <...> One of the user there commented: > I love LibreOffice, but see no need to shit-talk your competitor... And the LO folks who manage the page answer: > If a product locks people out of their OWN documents, even > when they've paid for it, that's not "sh*t-talking" – that's > pointing out how terrible that situation is! LibreOffice > stands on its own feet and we don't normally talk about > proprietary products, but it's important to make people aware > that there's an alternative... But of course, they won't say you that Writer will silently harm your documents. That it can silently remove the formatting or images. And that you will not be even aware about this until you open the documents later. And these documents, of course, can be very valuable. So, open-source folks blame Microsoft for the FUD propaganda, but the same FUD propaganda, mixed with a quasi-religious bullshit aka "help them to spreading the word" is what they use to promote their buggy crapware. And using LO is not really "free" for us, users. Saying that "LO doesn't cost you money, so you users cannot blame it" is bullshit. When you, developers and managers, know that your software have _so_ many bugs and _so_ many bugs have critical impact to the workflow, and these bugs are so easy for users to face with them, it is just unfair to promote your software as something that is ready for end-users, you simply lie them. They trust you, they think that "stable" releases are really stable (but in fact these releases are alpha ones) and "fresh" releases are unstable just a little (these releases are in fact pre-alpha ones), they spend days and weeks testing and reporting dozens and hundreds of bugs, they spend days and weeks fixing their broken documents because they hope that this nightmare is something occasional and temporary. But no, it is neither occasional nor temporary. I leave this message here not because I think it has any value to you, of course. But because it will be a good reminder for myself. And because it will be possible to provide a link to people who are thinking about to start using LO. I really don't care whether you ban me or not. But if someone think that I'm "just a random guy who never really tried LO", he/she can check the bugs I have reported for several years. There are many of them. I also have 2 additional account, so you can multiply this number by 3.
All of images were linked images, and were anchored as characters. Here is a comparision of the XML markup of the image that is still in the file and the XML of the image that is now missing: _This is a part of "covid.jpg" image. This image is OK, it wasn't removed._ ```xml <text:p text:style-name="P10"> <draw:frame draw:style-name="fr1" draw:name="Image2" text:anchor-type="as-char" svg:width="415.11pt" svg:height="587.31pt" draw:z-index="5"> <draw:image xlink:href="../covid.jpg" xlink:type="simple" xlink:show="embed" xlink:actuate="onLoad" draw:filter-name="<All images>" draw:mime-type="image/jpeg"/> </draw:frame> </text:p> ``` _And this is a part of the "house.jpg" image. This image is missing:_ ```xml <text:p text:style-name="P6"> <draw:frame draw:style-name="fr1" draw:name="Image1" text:anchor-type="as-char" svg:width="486pt" svg:height="273.34pt" draw:z-index="0"><draw:image/></draw:frame> </text:p> ``` It is very clear that the second snippet is broken. The only question is why. All of the images were inserted exactly the same way, by clicking the "Insert > Image" and enabling the "Link" check box. After the document was almost ready, I closed it, and then opened it again to edit some text. I have do it multiple times and the images were in their correct places. Then, two days ago, I opened this document again, and the images were missing, and XML markup is broken. It seems there was some internal error during the last save.
The same issue by Bo Siltberg https://www.mail-archive.com/users@global.libreoffice.org/msg56426.html Bo's document has about 1400 pages with about 1800 images. 100 of them were lost. Bo make a point that this might be due to the fact that the document is large. But in my case there were only 5 pages and 5 images.
Bug report makes sense only if reproducible. Can you make it so? Can you attach ODT, if no personal info? You should also search existing bugs, I guess you'll be terrified, there are many on images.
Please attach example files so we can test. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the files.
Dear John, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear John, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp