Description: Writer .odt file becomes randomly blank and zero bytes in a BitLocker encrypted external SSD in macOS 10.14 Mojave Steps to Reproduce: 1. Attach BitLocker encrypted Samsung T5 external SSD to MacBook Pro (2017) 2. Mount SSD with M3 BitLocker app (https://www.m3datarecovery.com/mac-bitlocker/) or BitLocker Anywhere for Mac (https://www.easyuefi.com/bitlocker-for-mac/bitlocker-for-mac.html) 3. Open Writer, create a small new .odt file. Open and save several times, make small changes here and there, exit Writer and save on exit. Do this several times and confirm random disappearance of the information contained on the file. --- Actual Results: .odt file became completely blank and all information on the file is lost. The information appears to be lost in conjunction with recent activities of saving or opening of the file. That is, soon after opening or closing/saving of the file. Expected Results: Save the changes and maintain integrity of the file. In the same exact environment and circumstances Microsoft Word does not display any errors or information lost. Reproducible: Sometimes User Profile Reset: No Additional Info:
SSD is formatted NTFS.
Given the very specific circumstances, it is unlikely that anyone from QA will be able to confirm this. How is the external SSD connected to the macOS system ? Currently, there is no way to tell whether this : - is a macOS problem ; - is a BitLocker problem ; - this is a LO problem. LO is not optimized for macOS. There's no way of telling whether LO's internal file representation memory management is compatible with the way BitLocker is designed to function on macOS. There have been reports in the past of similar problems affecting USB-connected drives (irrespective of whether or not they are encrypted). Perhaps the behaviour you are experiencing is comparable.
Does the problem also occur with a FAT/VFAT formatted file system on the SSD ?
SSD is connected through USB cable to Dell D6000 docking station. I have not attempted to reproduce the bug in a differently formatted SSD. If possible, I will test this when time permits. Thank you for looking into this potential bug.
Hello Alegoje, a new major release of LibreOffice is available since this bug was reported. 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. Please also try to answer the question from comment 3.
Dear alegoje, 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 alegoje, 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