I'm on Ubuntu 12.04.5 with all updates and LibreOffice Version: 4.4.1.2
Build ID: 40m0(Build:2) (libreoffice 1:4.4.1~rc2-0ubuntu1~precise1) from PPA.
Steps to reproduce:
1. I have shared my Public folder using nautilus-share (0.7.3-1ubuntu2), placed test.odt file in it.
2. I navigate Nautilus to smb://localhost, clicked Open in Terminal here (or launch terminal and "cd ~/.gvfs/public\ on\ localhost").
3. Run "libreoffice test.odt" in terminal.
4. Got "Document in Use" window with text:
Document file 'test.odt' is locked for editing by:
Unknown User
Open document read-only or open a copy of the document for editing.
Open Read-Only Open Copy Cancel
5a. If I click 'Open Read-Only' the document is opened in read-only.
5b. If I click 'Open Copy' the "Untitled 1" document is opened.
5c. Cancel closes this window.
Expected results:
The "test.odt" files is opened in read-write mode, user can edit it.
Actual results:
User can't edit original document (see pp. 4-5 above).
This functionality is essential. Please fix this bug.
The bug is somehow related to bug#72337.
I'm on Ubuntu 12.04.5 with all updates and LibreOffice Version: 4.4.1.2 rc2-0ubuntu1~ precise1) from PPA.
Build ID: 40m0(Build:2) (libreoffice 1:4.4.1~
Steps to reproduce:
1. I have shared my Public folder using nautilus-share (0.7.3-1ubuntu2), placed test.odt file in it.
2. I navigate Nautilus to smb://localhost, clicked Open in Terminal here (or launch terminal and "cd ~/.gvfs/public\ on\ localhost").
3. Run "libreoffice test.odt" in terminal.
4. Got "Document in Use" window with text:
Document file 'test.odt' is locked for editing by:
Unknown User
Open document read-only or open a copy of the document for editing.
Open Read-Only Open Copy Cancel
5a. If I click 'Open Read-Only' the document is opened in read-only.
5b. If I click 'Open Copy' the "Untitled 1" document is opened.
5c. Cancel closes this window.
Expected results:
The "test.odt" files is opened in read-write mode, user can edit it.
Actual results:
User can't edit original document (see pp. 4-5 above).
This functionality is essential. Please fix this bug.