[Libreoffice-bugs] [Bug 109520] New: "General input/output" opening a file through a symlink to a GVfs mount

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Thu Jul 27 13:37:55 UTC 2017


https://bugs.documentfoundation.org/show_bug.cgi?id=109520

            Bug ID: 109520
           Summary: "General input/output" opening a file through a
                    symlink to a GVfs mount
           Product: LibreOffice
           Version: 5.3.4.2 release
          Hardware: All
                OS: Linux (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: libreoffice-bugs at lists.freedesktop.org
          Reporter: rdiezmail-libreoffice at yahoo.de

I have written a script to help me mount Windows shares with GVfs, it's here:

https://github.com/rdiez/Tools/blob/master/MountWindowsShares/mount-windows-shares-gvfs.sh

The script is just a fancy wrapper that runs gvfs-mount and creates symbolic
links to all the mount points.
Without the symlinks, finding the mountpoints is awkward (for me).

I am using Ubuntu 16.04. I have installed Launchpad's "official" PPA to get
LibreOffice 5.3.

If I open a Writer document through a symbolic link like this:

/home/rdiez/WindowsShares/WindowsPcRdiez/Temp/MyDoc.doc

I then get this error:

General input/output error while accessing
/home/rdiez/WindowsShares/WindowsPcRdiez/Temp/MyDoc.doc

However, if I open the same file directly through the GVfs mountpoint (without
using the symlink):

/run/user/1000/gvfs/smb-share:domain=MY-WINDOWS-PC,server=my-windows-pc,share=rdiez,user=MYUSER/Temp/MyDoc.doc

Then it opens fine.

Other programs like Emacs can open the document file over the symlink without
problems.

1) The first issue is probably in Writer. It should report where the error is
coming from, and some sort of specific error message or error code, instead of
a generic error.

I mean that Writer is probably discarding error information along the way. That
makes it difficult to troubleshoot problems. This is not the first time I see
LibreOffice not reporting error causes accurately. This looks like a general
design or structural shortcoming in LibreOffice.

2) The underlying error is likely in some GVfs library, but it is difficult to
report or to argue with the GNOME developers without an real scenario where an
application hits the problem. That is the main reason why I am creating this
bug.

I hope that you could tell me (or even better, the GNOME developers) where
exactly this error is coming from, and what error code is being returned (that
Writer does not display to the user).

Many thanks in advance,
  rdiez

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20170727/2ea1e185/attachment.html>


More information about the Libreoffice-bugs mailing list