When in the More Info screen, back button exits the app, rather than returning to the Viewer.
@Jared - please provide explicit steps on what you're doing and what device you're using. On Nexus 7 2012 Model I open LibreOffice Viewer; Press dropdown (the three blocks in top right); Press "About" Press "More Info" Press the back arrow on Tablet (outside of viewer) Observed: About screen goes away and I end up back at the viewer home screen (able to open a recent document) Marking as NEEDINFO - please provide the additional information and mark as UNCONFIRMED. Thanks
I'm using a Samsung S4 Active with Android 4.4.2 I open the file from ES File Explorer (I do not see three dots or any settings button indicator). Click my hard Menu button Tap About Tap More Info Click hard Back button App exits back to ES File Explorer.
(In reply to Jared from comment #2) > I'm using a Samsung S4 Active with Android 4.4.2 > TESTING with: Nexus S, Android 4.4.4, LO 4.5-master (2f6bc9c) > I open the file from ES File Explorer (I do not see three dots or any > settings button indicator). I'm using File Manager v1.0.2 from CM Project > Click my hard Menu button I either click the 3-dots button or use the menu button on my device (end result is the same). > Tap About > Tap More Info > Click hard Back button Ayup > App exits back to ES File Explorer. CONFIRMED: I'm taken back to the File Manager. I'll mark this as NEW. I'm not quite sure if htis behavior is expected, but I would prefer the back button in this case to not completely exit out of LibreOffice.
** 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.0.5 or 5.1.2 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
** 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.2.7 or 5.3.3 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-20170522
I am now using a Moto X4 device with 6.1.0.0.alpha0+/484d0ea842da apk version. I cannot reproduce the crash any longer.