https://bz.apache.org/ooo/show_bug.cgi?id=128049
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |usability Summary|Error opening file from |Opening files on gvfsd-fuse |Samba share |filesystems through POSIX | |APIs fails with "General | |input/output error while | |accessing ..." --- Comment #6 from [email protected] --- (In reply to Pedro from comment #5) > (In reply to damjan from comment #4) > > > Now if I am correct, ALL these services would suffer from this bug, ie. > > opening an SSH filesystem in your file browser and trying to double-click on > > an .xls file there, would also get "General input/output error while > > accessing <filename>" in OpenOffice. (Can someone confirm?) > > Can you provide an example of an SSH filesystem? I'm not sure what that > means. For example if you install OpenOffice in a Linux guest VM in VirtualBox, with a NAT type network interface, your host IP address will be 10.0.2.2. And if you have a SSH server on the host, and you open a file manager in the guest, and type: sftp://10.0.2.2/ it should open the filesystem root (/) on the host machine. I've tested that and I can reproduce this bug with SSH too, so it's NOT Samba-specific. It is that notorious gvfsd-fuse bug I predicted earlier. > > This is the infamous gvfs bug: > > https://gitlab.gnome.org/GNOME/gvfs/-/issues/249 > > which breaks many other applications too (LibreOffice included, at least > > back in 2019), and has not been fixed in 9 years, and has little hope of > > being fixed upstream. > > This bug does not affect any other software (including LO). I can open any > file on these shared folders with any application, except for AOO under > Linux. AOO under Windows opens all files without issues This other Linux software probably does one of the following: - Uses simpler POSIX file APIs which work fine on gvfs-fuse. We cannot use the simpler APIs, because we do more advanced things with files, for example we probably seek to the file start multiple times, so each filter can detect the file type. - Uses GIO APIs directly instead of POSIX APIs ("option 2" in my previous post). Windows doesn't use FUSE and gvfsd-smb to access SMB, it does something else, probably an in-kernel SMB/CIFS filesystem. > > This should be pretty easy, as we already have a GIO content provider that > > could be used (in main/ucb/source/ucp/gio). It's probably also somewhat > > lighter and faster. > > Easy is better ;) Is this gvfs of any use? Maybe it can all be completely > removed? gvfs is a system component present on Linux distributions. We do not ship it and we end up using it unintentionally, because it acts as an implicit gio plugin. But we can use less of it, bypassing the problematic gvfsd-fuse component. > > But before we begin any development, can someone please test: > > 1. Does this bug happen with other filesystems such as SSH/SFTP? > > 2. What happens if you type the GIO URL to the file in the file open dialog? > > It probably looks something like "smb://cripsul/republica/folder/file.xls". In my own tests: 1. Yes, it happens with SSH/SFTP too. 2. The URL works, because it uses GIO directly, bypassing gvfsd-fuse. -- You are receiving this mail because: You are the assignee for the issue.
