Bug 43459 - Opening document fails when on samba mount with mixed OS windows/linux
Summary: Opening document fails when on samba mount with mixed OS windows/linux
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected)
3.4.4 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
: 48171 (view as bug list)
Depends on:
Blocks: Network
  Show dependency treegraph
Reported: 2011-12-02 01:29 UTC by luis.public.mail
Modified: 2023-01-16 03:21 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description luis.public.mail 2011-12-02 01:29:26 UTC

i have a  samba share (NTFS) on a SAS which is exported by a server running ubuntu (10.04 lucid)(samba: Version 3.4.7) to the users on a mixed windows/linux environment.
When i open a "not shared" spreadsheet  first from a PC under linux (opensuse 11.3) and after from a windows PC (XP,Vista) everything works correctly. I have a warning saying that the document is used and that only a copy can be opened or with read-only mode. The same happens when both computers are running the same OS.

But when i open first on windows and after on linux, i have an error when opening the document on linux: "General input/output error while accessing /path/to/file".

Exactly the same behaviour happens if the spreadsheet is "shared".

It seems not to be related to a recent update because i have tried with 3.4.4 but also with older versions (3.4.2,3.2).

The smb.conf:

        path = /path/2/dir
        valid users =  user1, user2
        read only = No
        create mask = 0777

fstab on linux:

//path/2/stations /mnt/linuxdir      cifs    user,noauto,iocharset=utf8,noserverino
Comment 1 elicoten 2013-02-20 10:05:40 UTC
Same problem on LibreOffice, Ubuntu 12.10.

If a Windows user has a spreadsheet open, and then Libreoffice on Ubuntu tries to open the same file, a "General Input/Output error whilst accessing <filename>" occurs.

The file is saved on a Windows (Samba) share.
Comment 2 dg1727 2014-02-09 08:57:01 UTC
*** Bug 48171 has been marked as a duplicate of this bug. ***
Comment 3 Joel Madero 2015-05-02 15:43:42 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2016-09-20 09:37:29 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2019-12-03 13:59:05 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2021-12-03 04:23:53 UTC Comment hidden (obsolete)
Comment 7 Gowit 2022-04-27 08:25:26 UTC Comment hidden (spam)
Comment 8 Julien Nabet 2022-06-18 14:33:37 UTC
On pc Debian x86-64 with LO Debian package, I don't reproduce this.

Here's what I did:
- created a Samba share on Linux machine
- created and saved an ods file with LO from Windows machine on the Samba share and let it opened
- opened the file from Linux machine
I tried with copy the file and read-only, both worked.

Could someone else give it a try? I may have missed something?
Comment 9 QA Administrators 2022-12-16 03:19:25 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2023-01-16 03:21:50 UTC
Dear luis.public.mail,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA 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 our bug tracker

Warm Regards,
QA Team