Operation not permitted while writing to symlinked fuse locations

Bug #1598183 reported by Dariusz Gadomski
56
This bug affects 10 people
Affects Status Importance Assigned to Milestone
gvfs
Expired
Medium
gvfs (Ubuntu)
Confirmed
Undecided
Unassigned
Nominated for Bionic by Dariusz Gadomski
Nominated for Cosmic by Dariusz Gadomski
Nominated for Wily by Dariusz Gadomski
Nominated for Yakkety by Dariusz Gadomski
Xenial
Confirmed
Undecided
Unassigned

Bug Description

Affected releases:
Ubuntu from 14.10+ (14.04 was working fine)

Steps to reproduce:
1. Setup a gvfs mount (I used smb and sftp shares configured via nautilus).
2. Create a symlink to the fuse-mounted location e.g.
cd ~/Desktop; ln -sf /run/user/1000/gvfs/smb-share:server=10.0.20.6,share=share1/symlinktest
3. Navigate with nautilus to the symlinked location, open a file available there with e.g. gedit or libreofficeand try to save it.

Expected result:
File is saved.

Actual result:
An enigmatic error message is displayed
(Cannot handle "file:" locations in write mode - for gedit, or "General input/output error while accessing <path>" for libreoffice).

The problems started with commit 548ba46c2ba51c4ec5b0dd8442b476f3a2a7000b fuse: Don't g_file_append_to unless O_APPEND is given. Reverting it makes the issue disappear.

I have rebuild gvfs enabling debugging (#define DEBUG_ENABLED 1) and here is what I got in ~/vfs.debug:
# accessing via symlink
vfs_open: /smb-share:server=10.0.20.6,share=share1/grouptest/symlinktest/test
open_common: flags=500002
vfs_open: -> Operation not supported
# accessing via /run/user/(...)
vfs_open: /smb-share:server=10.0.20.6,share=share1/grouptest/symlinktest/test
open_common: flags=1100000
setup_input_stream: have stream
setup_input_stream: doing read
vfs_open: -> Success

For reasons beyond my understanding the flags are different while accessing the file via the default gvfs-mountpoint causing the execusion to skip the modified section of client/gvfsdfusedaemon.c (returning -ENOTSUP).

I am attaching the full vfs.debug created.
Collapse All Comments
Expand All Comments
Add Comment

tags: added: sts
tags: added: regression-release
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gvfs (Ubuntu):
status: New → Confirmed
Changed in gvfs:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
Marc Neiger (marc-i) wrote :

using Mint 18 (ubuntu 16.04 xenial)
Opening files in such locations with libreoffice 5.2.0.4 generates the following message:
"General input/output error while accessing" xxxxx/xxxx/xxxx/

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gvfs (Ubuntu Xenial):
status: New → Confirmed
Revision history for this message
prof2004 (jdokupil) wrote :

Have this problem reported last year, and got a confirmed bug 1612708.

Was in the meantime back to 14.04 LTS, but now upgraded to 16.04.2 LTS because some drivers have been available only for this release.

The problem in 16.04.2 LTS still exists. Very sad :-(

Revision history for this message
dajare (dajare) wrote :

The problem still exists in 17.10. Even sadder. :'(

Changed in gvfs:
status: Confirmed → Expired
Revision history for this message
Dariusz Gadomski (dgadomski) wrote :

There is an upstream patch under consideration to be merged into master. Despite not being the perfect solution for the problem it fixes the issue.

Let's wait for it to be merged.

https://gitlab.gnome.org/GNOME/gvfs/issues/249

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.