Bug 65854 - Open read only fails when trying to open an already open document on a samba share
Summary: Open read only fails when trying to open an already open document on a samba ...
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.0.3.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-17 10:44 UTC by grahha
Modified: 2015-10-14 19:49 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
error dialog box (12.83 KB, image/png)
2013-06-17 15:00 UTC, grahha
Details

Note You need to log in before you can comment on or make changes to this bug.
Description grahha 2013-06-17 10:44:35 UTC
LibreOffice version: 4.0.3
OS: Ubuntu 12.04.2 / Windows 7 / Windows XP
File Share: Samba 3 on Ubuntu 11.04 server.
Hardware: x86 x86-64
Document types: writes, impress, calc 

What happens.
- UserA(window) opens document_1 on samba share. lock file gets created.
- UserB(ubuntu) tries to open document_1 on samba share.
- UserB gets prompted that file is already open and to choose, read only, open a copy, cancel.
- UserB selects read only:  gets presented with " general input/output error" dialog box.

What should happen
- UserA(windows) opens document_1 on samba share. lock file gets created.
- UserB(ubuntu) tries to open document_1 on samba share.
- UserB gets prompted that file is already open and to choose, read only, open a copy, cancel.
- UserB selects read only:  document opens in read only.
Comment 1 grahha 2013-06-17 15:00:50 UTC
Created attachment 80956 [details]
error dialog box

The error dialog box that appears when you try to open a document as read only on an already opened document
Comment 2 grahha 2013-06-20 09:33:12 UTC
This also prevents MS Office users from opening documents in read only if a LibreOffice user has the document already open.

MS Office 2007 on Windows 7 64bit
Comment 3 sweq1 2013-07-10 19:51:55 UTC
I have the same problem but with different configuration.

The file server :
Windows 2008 R2
Samba 2

LibreOffice 4.0.4
Document types: writes, impress, calc
MS Office 2003

Some scenarios :
Scenario 1 :
2 user with Ubuntu 12.04.2
user A open the LO file on the server, he's fine.
user B open the LO file on the server, a dialog box ask to open as read only or to copy the file, a second dialog box explain the file is corrupted.

Scenario 2 :
2 user with Ubuntu 12.04.2
user A open the MS file on the server, he's fine.
user B open the MS file on the server, a dialog box ask to open as read only or to copy the file, a second dialog box explain the file is corrupted.

Scenario 3 :
user A with Windows XP sp3
user B with Ubuntu 12.04.2
user A open the MS file on the server, he's fine.
user B open the MS file on the server, a dialog box ask to open as read only or to copy the file, a second dialog box explain the file is corrupted.

Scenario 4 :
user A with Ubuntu 12.04.2
user B with Windows XP sp3
user A open the MS file on the server, he's fine.
user B open the MS file on the server, the file is empty.
Comment 4 ign_christian 2013-07-11 04:54:59 UTC
I can also confirm behavior (general i/o error) on comment 0 with similar scenarios using simple sharing (no server) with Samba 3.5.14.

PC-A: Win XP with OOO 3.3.0
PC-B: PCLinuxOS KDE 32bit with LO 4.0.4.2
File to test: .doc

Scenarios:
- PC-B opens file in PC-A. PC-A will fails to open same file
- PC-A opens file in PC-A. PC-B will fails to open same file
- PC-B opens file in PC-B. PC-A will fails to open same file

But this scenario works:
PC-A opens file in PC-B. Then PC-B can opens same file as read only.

Note: That's not happen (file can be opened as read only) if 2 PCs using same OS (PCLinuxOS KDE 32bit) & same LO version (4.0.4.2).
Comment 5 Jan 2015-02-10 13:46:56 UTC
Tried this with Windows 7 and Ubuntu 14.04 LTS on a Samba share. LO Version: 4.2.7.2 Build ID: 420m0(Build:2). When I open a document in Powerpoint 2010 and try to open it in Libreoffice it will promt me to open it read-only which works just fine in my case.

Does the problem still occur for you with current Libreoffice versions?
Comment 6 Jan 2015-02-10 13:51:50 UTC
Tried with both the following combinations:
LO 4.4 (Linux) <-> LO 4.4 (Windows)
LO 4.5-dev (Linux) <-> LO 4.4 (Windows)
LO 4.4 (Linux) <-> Powerpoint 2010 (Windows)
Comment 7 QA Administrators 2015-09-04 02:55:56 UTC
Dear Bug Submitter,

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 INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/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

This NEEDINFO message was generated on: 2015-09-03
Comment 8 QA Administrators 2015-10-14 19:49:05 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO

Message generated on: 2015-10-14