Description: sort by settings is not saved for "unfortunately, lo viewer has stopped" Steps to Reproduce: change sort by settings to newest first, open attachment 130855 [details] from download directory on my device Actual Results: opening document, it shows error: unfortunately, lo viewer has stopped Expected Results: after clicking ok on error message, pressing back button on device, the sort by settings are reverted to default. this issue on version: 5.5.0.0.alpha0+ / build id : ec79f34 / android 5.1 Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Android 5.1; Mobile; rv:55.0) Gecko/55.0 Firefox/55.0
Cannot confirm Set "newest First" settings Open file, crash. On my device Is crash without error message "newest First" settings is still set Another issues is that sorting doesn't works at all . My files are sorted only alphabetically A-Z Version 5.5.0.0.alpha0+ Build ID: 076ed44
(In reply to raal from comment #1) > Cannot confirm > Set "newest First" settings > Open file, crash. On my device Is crash without error message > "newest First" settings is still set > > Another issues is that sorting doesn't works at all . My files are sorted > only alphabetically A-Z > > Version 5.5.0.0.alpha0+ > Build ID: 076ed44 Hi raal, could you please report the crash in a different issue ?
Hello krishna, Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ? You can install it alongside the standard version. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
(In reply to Xisco Faulí from comment #2) > (In reply to raal from comment #1) > > Cannot confirm > > Set "newest First" settings > > Open file, crash. On my device Is crash without error message > > "newest First" settings is still set > > > > Another issues is that sorting doesn't works at all . My files are sorted > > only alphabetically A-Z > > > > Version 5.5.0.0.alpha0+ > > Build ID: 076ed44 > > Hi raal, > could you please report the crash in a different issue ? Hi Raal, is this issue still reproducible in master?
reproducible the pptx no longer crashes mentioned in my original report however i tried another docx file, it shown message "unfortunately lo has stopped" the settings have changed to a to z, instead of newest first Version: 6.1.0.0.alpha0+ core:7ea2311ab734d19b705cf98aa9506cbe122e74e4 tinderbox: pull time 2018-02-09 17:44:16 tinderbox: buildname: Android-ARM@24-Bytemark-Hosting lyf flame 3, android 5.1
Hi Krishna, Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ?
Dear krishna [:kr1shna], This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear vihsa, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp