Created attachment 113215 [details] Presentation with links to videos. Since latest release on 5th February 2015, I can no longer open my Impress document. This document opened okay with previous build. Document attached. No other files were open.
(In reply to Steve from comment #0) > Since latest release on 5th February 2015, I can no longer open my Impress > document. This document opened okay with previous build. Document attached. > No other files were open. TESTING with LO 4.4.0.3 + Ubuntu 14.04, I can open attachment 113215 [details] without any errors. TESTING on Android, I'm having problems downloading the presentation file. Could you please try to trim-down the size of the presentation file and see if still has problems opening? Status -> NEEDINFO (Please change status of the bug back to UNCONFIRMED after you try trimming-down the file. Thanks!)
(In reply to Robinson Tryon (qubit) from comment #1) > (In reply to Steve from comment #0) > > Since latest release on 5th February 2015, I can no longer open my Impress > > document. This document opened okay with previous build. Document attached. > > No other files were open. > > TESTING with LO 4.4.0.3 + Ubuntu 14.04, I can open attachment 113215 [details] > [details] without any errors. > > TESTING on Android, I'm having problems downloading the presentation file. Just copied the file directly to my device. Testing with Android 4.4.4 + LO Viewer from F-Droid Version 4.5.0.0.alpha0+/7f68f67 - Added on 2015-02-06 The first slide opens, but I can't seem to move to the 2nd slide, edit notes, etc, so Status -> NEW
(In reply to Robinson Tryon (qubit) from comment #2) > Testing with Android 4.4.4 + LO Viewer from F-Droid > Version 4.5.0.0.alpha0+/7f68f67 - Added on 2015-02-06 > > The first slide opens, but I can't seem to move to the 2nd slide, edit > notes, etc This document now opens for me (albeit a bit slowly), and navigation works as well. https://wiki.documentfoundation.org/Documentation/Android#Impress Steve: How are you installing LibreOffice (Google Play, F-Droid, etc..)? Status -> NEEDINFO
Reproducible with Version: 4.5.0.0.alpha0+ Build ID: 6ef2c67 (Google Play) under Android 4.3 on GT-I9300 (In reply to Robinson Tryon (qubit) from comment #3) Maybe memory issue? I have a total of ~831 MB, ~180 free before opening
Crash when opening this file Version: 5.1.0.0.alpha1+ Build ID: 8dc648d java.lang.RuntimeException: Unable to start activity ComponentInfo{org.example.libreoffice/org.libreoffice.ui.LibreOfficeUIActivity}: java.lang.NullPointerException at android.app.ActivityThread.performLaunchActivity(ActivityThread.java) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java) at android.app.ActivityThread.access$800(ActivityThread.java) at android.app.ActivityThread$H.handleMessage(ActivityThread.java) at android.os.Handler.dispatchMessage(Handler.java) at android.os.Looper.loop(Looper.java) at android.app.ActivityThread.main(ActivityThread.java) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:515) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:788) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:604) at dalvik.system.NativeStart.main(Native Method) Caused by: java.lang.NullPointerException at org.libreoffice.ui.LibreOfficeUIActivity.onRestoreInstanceState(LibreOfficeUIActivity.java:629) at android.app.Activity.performRestoreInstanceState(Activity.java) at android.app.Instrumentation.callActivityOnRestoreInstanceState(Instrumentation.java) ... 12 more
** 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.1.6 or 5.2.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-20161108
Christian Lohmaier committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=2ff6afcce2c4df59d81f9d07cd9b7ffda00da479 tdf#89215 only process state changes after TileProvider is ready It will be available in 6.1.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
A polite ping to Christian Lohmaier: is this bug fixed? if so, could you please close it as RESOLVED FIXED ? Thanks
(In reply to Xisco Faulí from comment #8) > A polite ping to Christian Lohmaier: is this bug fixed? if so, could you > please close it as RESOLVED FIXED ? Thanks Closing this one. Thanks Christian Lohmaier for the fix!