A couple of times now on a low resource laptop I've had the following puzzling problem but the error message is incorrect... I try to open a file (in this case the latest problem was with impress) and a dialogue opens to say the file is corrupt and should LO repair it. However you answer the next thing is another dialogue opens up to say the file couldn't be opened. The cause of this is a lack of temp file space - in this case my root partition is small and a build up of old packages from updates causes it to run out of room every now and again. Cleaning up the filesystem fixes the problem by freeing temp space.
Could you please paste the info from Help - about LibreOffice ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the information has been provided
Dear ffs, 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
Apologies I missed the NEEDINFO request... I don't think this problem is linked to a particular version of LO - it's been here for years. However for the record: Version 6.3.4.2 Build ID: 1:6.3.4-0Ubuntu0.18.04~Io2 CPU Threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; My interpretation of the problem is /tmp fills up and is needed during file opening. The disk full error or can't write / can't open error is thrown as "file corrupt". An obvious fix for me is to resize my root partition but this only ever occurs when I'm short of time so I've never remembered to do it. The confusing nature of the error causes minor frustration until I recall it is time to do some cleaning.
Looks like a duplicate. *** This bug has been marked as a duplicate of bug 124925 ***