It was possible to open a ".odt" file on owncloud server, successfuly. Soon after #96771. A new attempt to open the very same file was not successful. Viewer crashed with an error message, "LibreOffice Viewer stopped". Needs an re-install or wait for unknown amount of time for Viewer to be work again on owncloud documents. Steps to reproduce: - Follow steps on #96771 - Try to open another file which don't have special chars in file name Platform(s): Owncloud: 8.1 Android Viewer: 5.2.0.0.aplha0+ CyanogenMod: 13
TESTING on Android 5.1.1 with 5.3.0.0.alpha0+: tinderbox: buildname: Android-ARM@24-Bytemark-Hosting tinderbox: tree: MASTER tinderbox: pull time 2016-08-04 00:59:32 core:f2da3173f8 (In reply to Faruk Uzun from comment #0) > - Follow steps on #96771 Unless the repro steps are pages long, it's most convenient for us to have all of the steps copied over to each new bug report. Feel free to re-use any existing test documents by linking to them with autolinkification (http://bugzilla.readthedocs.io/en/latest/using/tips.html#autolinkification) -- > Steps to Reproduce > > 1) Connect to an owncloud server Testing with demo.owncloud.org Set up ownCloud settings in "..." -> Storage provider settings user = test pass = test > 2) Try to open a file which have spaces in filename Using the file 'Demo Textfile - License.txt' which is located at the top-level directory, when I click on the file, Android Viewer crashes. > - Try to open another file which don't have special chars in file name Using README.md (also at top-level of demo.owncloud.org). When I click on the file, Viewer tries to open it but crashes. > Needs an re-install or wait for unknown amount of time for Viewer to be work > again on owncloud documents. I force-quit the app and wiped the app data, then restarted the app and re-entered the ownCloud url and credentials. Using README.md again, when I click on the file, Viewer succeeds at opening it (no crash). So I'll call this bug CONFIRMED. Status -> NEW
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170901
Dear Faruk Uzun, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
No assertion failure mentioned, removing from Assert meta bug.
ownCloud access in the app is currently more generally broken and needs some more work altogether. Closing as a duplicate of bug 129833, which is used to keep track of that work. *** This bug has been marked as a duplicate of bug 129833 ***