<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - FILESAVE general input/output error on save, files truncated" href="https://bugs.documentfoundation.org/show_bug.cgi?id=113138#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - FILESAVE general input/output error on save, files truncated" href="https://bugs.documentfoundation.org/show_bug.cgi?id=113138">bug 113138</a> from <a class="email" href="mailto:tupsuosu@gmail.com" title="Saskia S <tupsuosu@gmail.com>"> Saskia S</a> <pre>Similar, but not quite identical situation here: LO 6.2.5.2 on Arch Linux running Linux 5.2.6 kernel; in my case the error was clearly linked to saving a relatively large (340 KiB) .docx file into Dropbox and then attempting to save again (regardless of save destination). Very small files appear unaffected; I tested this by creating a new .docx file, saving to Dropbox, adding more text and saving again (with no error). This seems to implicate Dropbox as doing *something* with the file that causes LO to consider it corrupt/otherwise unsaveable in this case; could it be that in the original filer's case, the network drive management software or in the last two reports, something else running is altering the files whilst LO still has them open? <a href="https://ask.libreoffice.org/en/question/134688/general-inputoutput-error-keeps-destroying-my-work/">https://ask.libreoffice.org/en/question/134688/general-inputoutput-error-keeps-destroying-my-work/</a> This describes a set of similar issues. <a href="https://ask.libreoffice.org/en/question/134688/general-inputoutput-error-keeps-destroying-my-work/?answer=168551#post-id-168551">https://ask.libreoffice.org/en/question/134688/general-inputoutput-error-keeps-destroying-my-work/?answer=168551#post-id-168551</a> This comment in particular seems to come to the same conclusions as me with regards to Dropbox. One very simplistic workaround that seems to work just fine is to copy the entire contents of the affected document into a new file (via creating a new, empty document in LO) and then saving it in a different location. I'm unsure if this helps with the version in which the bug takes place while saving locally, but it might be worth a try.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>