After upgrading from LibreOffice 4.1.2 to 4.1.3 (Ubuntu repository) I'm getting always the error message "Not all attributes could be read." on opening a document. This happens also if I'm opening a newly created document. Steps to reproduce: 1. Open LibreOffice Calc. 2. Save the empty document anywhere. 3. Close LibreOffice Calc. 4. Open LibreOffice Calc. 5. Open the newly created document. 6. After opening the document the error message "Not all attributes could be read." will appear. I have also deleted my profile in ~/.config/libreoffice but the error message still appears.
Please try purging libreoffice completely and then reinstalling and let us know if that solves it. This is weird - I haven't seen it. Ubuntu 13.10
Bjoern - here is an interesting one. I surely can't reproduce but thought you might have additional input on what could be causing this :-/
Setting to NEEDINFO until Joel's request is answered. After providing the requested info, please reset this bug to UNCONFIRMED. Thanks :)
Purging LibreOffice has not solved the issue but I'm on Ubuntu 14.04 dev.
Edit: Interestingly the bug also appears on opening writer documents. But the error is there "General Error".
Hi SwordDragon, just to be sure: opening any writer document produces "General Error"? What happens if you just open writer? Same? Is this bug still valid / reproducible with the latest pre-release 4.2.0.1: http://www.libreoffice.org/download/pre-releases/ Should this be still reproducible for you with the latest LO release please set this bug back to UNCONFIRMED. Should this issue be solved set it to WORKSFORME. Setting to NEEDINFO until more detail is provided.
> Hi SwordDragon, just to be sure: opening any writer document produces "General > Error"? Correct. > What happens if you just open writer? Same? All is working fine then. > Is this bug still valid / reproducible with the latest pre-release 4.2.0.1: http://www.libreoffice.org/download/pre-releases/ I have tested it with with the upstream version 4.1.4.2 first and the bug doesn't appear there anymore. Either it is fixed or it is related to the ubuntu version. If there is a new version in the ubuntu repository and the bug appears again I will report it on Launchpad.