I opened Android viewer . I tried to open a Write document. The application stopped working. I tried it twice and it stopped both times.
This is not a blocker - please do not set priority unless you know our workflow. Removing blocker status.
Please attach a document that causes this problem. Marking as NEEDINFO - once you attach a document, set to UNCONFIRMED. Thank you
*** Bug 89891 has been marked as a duplicate of this bug. ***
Created attachment 115046 [details] A password-protected ODT Rproducible with Version: 4.5.0.0.alpha0+ Build ID: 6ef2c67 under Android 4.3 on GT-I9300 The attachment is protected with single-character password "1".
Hmm. trying to open it even corrupts the application's cache, so it cannot open any document after that until you go to Systemsettigs → manage apps → LibreOffice Viewer → clear cache → bump prio/severity. (note that not being able to open password-protected files is bug#89175 - but of course failing to open a document shall not render the app useless)
(In reply to Christian Lohmaier from comment #5) > Hmm. trying to open it even corrupts the application's cache, so it cannot > open any document after that until you go to Systemsettigs → manage apps → > LibreOffice Viewer → clear cache → bump prio/severity. > (note that not being able to open password-protected files is bug#89175 - > but of course failing to open a document shall not render the app useless) Hi, I have this issue on all files on Android 4.3 with recent release of (5.0.0.0.alpha1+/ab465b9/). All gmail attached files and downloaded files opens as read-only / password protected in fact they are not (but experimental editor works) I can only open a file -once- the second time -even the same file- Viewer stops working, need to clear the cache- delete files... Should i open a different bug report, because i can reproduce this issue non-password protected files. Best regards, Zeki
with upcoming version no reason to manually clear the cache anymore, but opening pw-protected documents still is missing feature. Setting duplicate. the other problem is dealt with alongside bug#93281 *** This bug has been marked as a duplicate of bug 89175 ***