Download it now!
Bug 38419 - Cannot access files accross network from LO module
Summary: Cannot access files accross network from LO module
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.3 release
Hardware: x86 (IA32) Linux (All)
: high major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-17 10:00 UTC by Planas
Modified: 2015-07-18 17:27 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Planas 2011-06-17 10:00:24 UTC
Users report that they can not access files from within LO on network drives. The files can sometimes be opened in LO through the file manager. This has been reported for Fedora 14/64 bit, Fedora 15/32 bit, Ubuntu 11.04, and Ubuntu 10.10.
The file manager used in one instance was Nautilus and it is assumed the distro's default file manager was used with the default GUI.

One user (Ubuntu) reported nothing happens when trying to open files from within LO and a General Input/Output error is reported when saving a files.

Both LO 3.4.0 and 3.3.2 are reported to have this problem. OOo (version unspecified) was able to access the files correctly from Ubuntu 10.10. 

The thread can be found at the following link for more information:

HTTP://nabble.documentfoundation.org/General-input-output-error-when-saving-to-network-drive-tp3061786p3074966.html
Comment 1 Steve Edmonds 2011-06-20 22:43:37 UTC
Hi.
This is not an issue with a Stardom NAS unit with OSX + LO3.3.4 or Suse 11.0 + 3.3.2.
Comment 2 Dave K 2011-07-06 22:08:57 UTC
I was having the same issues; I was OK opening a file on a samba share, but could not save the file (to the existing filename; I was fine saving to a brand new filename).  The error generated was "General input/output error while accessing <filename>".

This was solved when I discovered the following post:
http://ubuntuforums.org/showpost.php?p=6012786&postcount=691

So basically, according to that post, the fault is with the office program not implementing cifs style mandatory byte range locks.  It was solved/worked around by adding "nobrl" to the cifs mount options.

Everything is OK now, but I presume that libreoffice needs to fix up byte range locks, for better compatibility with network file access.
Comment 3 Bret R 2011-11-15 17:04:19 UTC
I have just been searching for a solution to a similar problem and thought I would add to the discussion, as it's been happening to me on Win7 64-bit with both LO 3.3.x and 3.4.x. The server in question is a Hammer network drive from a few years ago, and ours is a Windows network.

I can open document files with images across the network, but they report a General Input/Output error when saving, and the files needs to be recovered when LO is started again. When I get this error message in a document, I notice that the document's embedded images break and report a Read_Error problem.

(I get a similar error with one of our office's large Calc spreadsheets as well, particularly when the sheet structure is changed, but it is intermittent, and while I think it's macro-related, I haven't nailed down what the trigger is.)
Comment 4 William 2011-11-23 01:14:56 UTC
I have the same issue.

We are running libreoffice in our office and i can't save a file as.

Then i get a general imput/output error.
i'm running this from ubuntu 11.04 i already patched gvfs with 2 patches upstream but that did not fix this issue.

When saving a file with gedit it does work.

With kind regards,

William
Comment 5 Björn Michaelsen 2011-12-23 12:21:30 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 6 Marco Iora 2012-01-16 05:15:28 UTC
(In reply to comment #3)
> I have just been searching for a solution to a similar problem and thought I
> would add to the discussion, as it's been happening to me on Win7 64-bit with
> both LO 3.3.x and 3.4.x. The server in question is a Hammer network drive from
> a few years ago, and ours is a Windows network.
> 
> I can open document files with images across the network, but they report a
> General Input/Output error when saving, and the files needs to be recovered
> when LO is started again. When I get this error message in a document, I notice
> that the document's embedded images break and report a Read_Error problem.
> 
> (I get a similar error with one of our office's large Calc spreadsheets as
> well, particularly when the sheet structure is changed, but it is intermittent,
> and while I think it's macro-related, I haven't nailed down what the trigger
> is.)

Same problem here, on Windows xp with LO 3.4.3, 3.4.4, 3.4.5, LO 3.5.0beta1, LO 3.5.0beta3.

What happens in my tests is as follow:
1) I open an odt, shared on alfresco cifs. No Errors.
2) I make a little change and save. Error saving document, General I/O Error. But the document is saved anyway.
3) I make another little change and save. LO notifies that document has been changed after opening and asks to overwrite. If i choose to overwrite then LO gives a Error during file save. Any further save gives this error.
Comment 7 Olivier ROCH VILATO 2012-05-18 03:23:42 UTC
Same problem on Windows XP, Windows 7 with LO 3.5.2 on an alfresco 4 CIFS share

Any solution ?
Comment 8 Julien Nabet 2014-12-02 21:35:59 UTC
Planas and those who didn't mention Alfresco: would you have some time to give a try to a recent LO version (last stable one is 4.3.4)?

For those who talk about Alfresco, there are several types of network access, Alfresco is just one of them. So please open a new bugtracker if you still encounter with Alfresco 4 since the original description doesn't quote Alfresco.
Comment 9 QA Administrators 2015-06-08 14:28:58 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/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!

This NEEDINFO Message was generated on: 2015-06-08

Warm Regards,
QA Team
Comment 10 QA Administrators 2015-07-18 17:27:34 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-07-18