Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMartin Schuppert
2013-09-25 08:32:44 UTC
Description of problem:
When use "Connect to server" in Nautilus Configure and configure a webdav share it is not possible to rename files or folders.
The following messages will be displayed:
"The item could not be renamed. Sorry, could not rename "dir1" to "dir2": The specified location is not mounted".
"The item could not be renamed. Sorry, could not rename "file1" to "file2": The specified location is not mounted".
Version-Release number of selected component (if applicable):
* RHEL 6.4
* gvfs-1.4.3-15.el6.x86_64 ( webdav backend )
* nautilus-2.28.4-19.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. Setup basic webdav server
2. use "Connect to server" in Nautilus Configure and configure a webdav share
3. create a file/directory
4. rename file/directory which results in an error message
Actual results:
Error message is being displayed:
"The item could not be renamed. Sorry, could not rename "file1" to "file2": The specified location is not mounted".
Expected results:
No error message, the file/directory will be renamed
Additional info:
Ref:
https://bugzilla.gnome.org/show_bug.cgi?id=579276https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/512496
Solved upstream:
The problem here was that the path the backend supplied back to the client was
relative to the mount_prefix of the mount; so the client needs to resolve that
path and append the mount_prefix before creating a new GDaemonFile with the new
path.
Fixed on master with the following commit:
commit d4049d3ac0741c3700a029a24c869dfafd840dc2
Author: Christian Kellner <gicmo>
Date: Thu May 12 10:53:04 2011 +0200
daemonfile: Re-root the path in set_display_name ()
The path we get as a result of a set_display_name operation has to be
re-rooted with the mount_prefix of the specific mount.
This fixes the "Location not mounted" error that we currently get for
e.g. WebDAV mounts with a mount_prefix after renaming of files.
And the supportive commits:
commit 7a2942f7bdf39ebfc31ea90c0685b5890d30964d
commit 66bc0189d836130768df41900f3cf29723bbd870
Comment 3RHEL Program Management
2013-10-13 23:07:02 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2014-1499.html