Created attachment 138793 [details] Screen shot of document with missing graphic While editing a document, existing graphics elements (imported, not linked PNG images) are lost. Document is corrupted, shows "Read Error" where graphic was just recently. Windows 10 64-bit, PC has 16GB Ram.
I know there are pbs with image management on LO but would it be possible you attach a document with a step by step process to reproduce this? Indeed without more indication, I don't know how you may be helped. Also, you can give a try to brand new 5.4.4
The only known steps to reproduce something like this are for impress (bug 98686 comment 16) Some similar reports Bug 108689 Bug 112422 https://ask.libreoffice.org/en/question/135639/large-document-images-disappear/
Dear Bug Submitter, 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-20180703
This is a long-standing bug. Reproduce by: 1) create a text or impress document 2) add a bunch of large JPG and/or OLE components 3) leave LibreOffice running for a while 4) observe your corrupted document Because of this and numerous compatibility problems, we and our customers have sadly switched back to MS for important documents... Latest PC where this problem observed: Windows 10 64-bit, PC has 32GB RAM.
(In reply to Dave Nadler from comment #4) > This is a long-standing bug. > Reproduce by: > 1) create a text or impress document > 2) add a bunch of large JPG and/or OLE components > 3) leave LibreOffice running for a while > 4) observe your corrupted document > Because of this and numerous compatibility problems, > we and our customers have sadly switched back to MS > for important documents... > Latest PC where this problem observed: Windows 10 64-bit, PC has 32GB RAM. Hopefully fixed with LibreOffice 6.1. See: https://blog.documentfoundation.org/blog/2018/06/19/image-handling-rework-for-libreoffice-collaboras-tender-results/ RC1 is available at https://wiki.documentfoundation.org/QA/BugHuntingSession/6.1.0RC1 Please give it a try & report the results.
> RC1 is available at > https://wiki.documentfoundation.org/QA/BugHuntingSession/6.1.0RC1 > > Please give it a try & report the results. Could you please try to reproduce it with LibreOffice 6.1 RC1 ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the build
Created attachment 144485 [details] example large image 1
This problem has just occurred again with an ODT in the latest version. Version: 6.0.5.2 (x64) Build ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16 CPU threads: 8; OS: Windows 10.0; UI render: default; Locale: en-US (en_US); Calc: group As before, the document was left open for a few days and Windows 10 sleep-restart cycles, and the graphics were hosed. I've attached a large image (one of the ones lost in the document). Import it into a document a few times, leave Libre Office running, and after a while they'll get hosed.
Another related weirdness: After this happened, I tried to open an older document and got the same error. I closed ALL instances of LibreOffice components, and then was able to open the older document without error (images appeared where previously I'd got an error box).
I've noticed that this seems to often happen when Windows is suspended and resumed; document is OK in evening, next morning on resume its got "Error". Happened again this morning with a document containing 3 pictures. Version: 6.0.5.2 (x64) Build ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16 CPU threads: 8; OS: Windows 10.0; UI render: default; Locale: en-US (en_US); Calc: group
(In reply to Dave Nadler from comment #10) > I've noticed that this seems to often happen when Windows is suspended and > resumed; document is OK in evening, next morning on resume its got "Error". > Happened again this morning with a document containing 3 pictures. > > Version: 6.0.5.2 (x64) > Build ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16 > CPU threads: 8; OS: Windows 10.0; UI render: default; > Locale: en-US (en_US); Calc: group Thanks for all the updates. However, the big question is, is still reproducible with 6.1. LibreOffice 6.1 contains a lot of changes related to image handling (which won't be in LibreOffice 6.0 branche). Please give it a try (www.libreoffice.org).
Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists in 6.1. Change to RESOLVED WORKSFORME, if the problem went away.
Dear Bug Submitter, 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 Dave Nadler, 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