Description: Was using LibreOffice_6.1.5_Win_x64.msi Upgraded to LibreOffice_6.1.6_Win_x64.msi After upgrading, double-clicked on my encrypted spreadsheet (previously encrypted using Excel). Lo & behold: did NOT get prompted for a password: it just opened without one. Notes: On all previous occasions (using 6.1.5) I was prompted for a password. On 1st occasion using 6.1.6 I wasn't prompted, but spreadsheet opened normally. Then tried the self-same spreadsheet on another PC using Excel, and it opened normally, i.e. without a password. The clear implication here is that the spreadsheet was being stored non-securely by 6.1.5 but always prompting for a password. Not nice, since I need to keep this data secure as (e.g.) an email attachment and while being stored on someone else's sever. Thanks, Huw (retired software InJineer!) Steps to Reproduce: 1. Store encrypted spreadsheet in LibreOffice 6.1.5 2. Upgrade to LibreOffice 6.1.6 3. Open spreadsheet in LibreOffice 6.1.6 --> Calc Actual Results: The "encrypted" spreadsheet opened OK without first prompting for a password. Same result for both Calc and Excel Expected Results: The spreadsheet should first have prompted for a password. Or, rather, the spreadsheet should have been encrypted! Reproducible: Always User Profile Reset: No Additional Info: Just a thought... On the run-up to this problem, LibreOffice-->Calc 6.1.5 crashed while this spreadsheet was open and had been idle for an hour or so. Hence had to go through the recovery routine which involved entering the password twice. In fact, it was this instability that prompted me to upgrade to 6.1.6. From now on, I'll keep an eye on 6.1.6 Calc and check every so often that the spreadsheet is, indeed, encrupted. Ho-hum!
It's happened again on Calc version 6.1.6 I just installed. ...and on my trusty Windows-7 64-bit PC. And I'm pretty certain it's a side-effect introduced when Calc occasionally "hangs". I.e. becomes completely unresponsive. - Calc hangs from time to time - I use Windows Task Manager to terminate Calc. - Then double-click on my spreadsheet - This now goes into a recovery mode, losing recent changes. - The recovery is otherwise Ok, and involves entering the password twice. - When next saved, the spreadsheet is no longer encrypted. - I.e. Neither Calc nor Excel prompt for a password. Hope this helps. Huw
Thank you for reporting the bug. it seems you're using an old version of LibreOffice. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear huw, 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 huw, 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