Description: Libre office keeps saying it must open files in read-only mode as it 'doesnt have access rights' even though it actually should be able to. It is also inconsistent, sometimes it works, sometimes it doesnt, and sometimes it aligns with when dropbox is uploading the file after I save it. Steps to Reproduce: 1. Open a file in a dropbox folder (both docx and xlsx) 2. 3. Actual Results: Forces me to open a copy and save as a new name if I want to edit the document/xlsx Expected Results: Should be able to edit the file directly and save it Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-GB Module: SpreadsheetDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no
Please clarify your Dropbox usage. Is this against a cached file, locally created on this system, or was file created elewhere and sync'd to the Dropbox folder on this system, or are you using a Dropbox Pro 'cloud' instance of the file? Do you get correct opening (no need to save as a copy) if you change the filemanager over to LibreOffice's internal? Done with Tools -> Options -> Advanced 'Open Expert Configuration' button, then search in the dialog for "UseSystemFileDialog" and Edit to set it 'false' and 'OK' out. We do not implement the Dropbox API, and Dropbox is not CMIS compliant so changing the file manager might make no difference--if no difference, change it back setting "UseSystemFileDialog" 'true' The issue then is likely to be the lock file mechanism--LibreOffice's or Dropboxe's. We can't do anything about Dropbox's, but you can disable LibreOffice's, again from expert configuration, searching for and setting these stanzas false: 'UseLocking' 'UseDocumentSystemFileLocking' 'UseDocumentOOLockFile' For my local Dropbox cache/sync, setting 'UseLocking' false does not generate the lockfile, and would not be pushed up to Dropbox cloud--but I didn't check yet to see if there is a Dropbox generated lock present in a sync'd folder on another system. Have not dug out the code, but I think the UseDocumentSystemFileLocking is a CMIS signal, so maybe not applicable.
Dear Richard, 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
Problem seems to have resolved itself with the latest version of Libreoffice
(In reply to Richard from comment #3) > Problem seems to have resolved itself with the latest version of Libreoffice Thanks for retesting with the latest version. Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.