This bug is somehow related to other - LibO 72337 [1].
I'm on Ubuntu 12.04.5 with all updates and LibreOffice 3.5.7.2
Build ID: 350m1(Build:2)
(libreoffice 1:3.5.7-0ubuntu7) from official repository.
The problem exists in more modern versions of LibreOffice from PPA (3.6.6-0ubuntu1~precise1~ppa1 , 4.0.4~rc2-0ubuntu1~precise1 , 4.1.6-0ubuntu1~precise1~ppa1 , 4.2.8~rc2-0ubuntu1~precise1 , 4.3.6~rc2-0ubuntu1~precise1 , 4.4.1~rc2-0ubuntu1~precise1).
Steps to reproduce:
1. I have shared Public folder (read write, allow guest) from other Ubuntu 12.04.5 laptop using nautilus-share (0.7.3-1ubuntu2), placed test.odt file in it.
2a. I navigate Nautilus on other laptop to smb://laptop/public, clicked 'Open in Terminal here' (or launch terminal and "cd ~/.gvfs/public\ on\ laptop"). Run "libreoffice test.odt" in terminal.
2b. I navigate Nautilus on other laptop to smb://laptop/public, clicked on 'test.odt' file.
3. 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
4a. If I click 'Open Read-Only' the document is opened in read-only.
4b. If I click 'Open Copy' the "Untitled 1" document is opened.
4c. 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. 3-4 above).
This functionality is essential. Please fix this bug.
Notes:
If I try to open document with the command 'libreoffice smb://laptop/public/test.odt' I run into other bug (bug 1214352).
If I use windows SMB/CIFS server I can open and edit document from share.
My test results are located in Google Drive Table ( http://goo.gl/jY9Ubj ).
This bug is somehow related to other - LibO 72337 [1].
I'm on Ubuntu 12.04.5 with all updates and LibreOffice 3.5.7.2 0ubuntu1~ precise1~ ppa1 , 4.0.4~rc2- 0ubuntu1~ precise1 , 4.1.6-0ubuntu1~ precise1~ ppa1 , 4.2.8~rc2- 0ubuntu1~ precise1 , 4.3.6~rc2- 0ubuntu1~ precise1 , 4.4.1~rc2- 0ubuntu1~ precise1) .
Build ID: 350m1(Build:2)
(libreoffice 1:3.5.7-0ubuntu7) from official repository.
The problem exists in more modern versions of LibreOffice from PPA (3.6.6-
Steps to reproduce: public, clicked 'Open in Terminal here' (or launch terminal and "cd ~/.gvfs/public\ on\ laptop"). Run "libreoffice test.odt" in terminal. public, clicked on 'test.odt' file.
1. I have shared Public folder (read write, allow guest) from other Ubuntu 12.04.5 laptop using nautilus-share (0.7.3-1ubuntu2), placed test.odt file in it.
2a. I navigate Nautilus on other laptop to smb://laptop/
2b. I navigate Nautilus on other laptop to smb://laptop/
3. 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
4a. If I click 'Open Read-Only' the document is opened in read-only.
4b. If I click 'Open Copy' the "Untitled 1" document is opened.
4c. 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. 3-4 above).
This functionality is essential. Please fix this bug.
Notes: public/ test.odt' I run into other bug (bug 1214352). goo.gl/ jY9Ubj ).
If I try to open document with the command 'libreoffice smb://laptop/
If I use windows SMB/CIFS server I can open and edit document from share.
My test results are located in Google Drive Table ( http://
1. https:/ /bugs.documentf oundation. org/show_ bug.cgi? id=72337 .
ProblemType: Bug ature: Ubuntu 3.13.0- 46.77~precise1- generic 3.13.11-ckt15 dules: nvidia
DistroRelease: Ubuntu 12.04
Package: libreoffice 1:3.5.7-0ubuntu7
ProcVersionSign
Uname: Linux 3.13.0-46-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: amd64
Date: Tue Mar 10 23:52:04 2015
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MarkForUpload: True
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)