Bug 98886 - KIO slaves cannot move or copy files directly from one remote server to another
Summary: KIO slaves cannot move or copy files directly from one remote server to another
Status: CONFIRMED
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: git master
Platform: RedHat Enterprise Linux Linux
: NOR major
Target Milestone: ---
Assignee: David Faure
URL:
Keywords: triaged
: 302448 307693 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-02-08 23:27 UTC by Mike Jones
Modified: 2021-01-12 22:32 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Jones 2005-02-08 23:27:00 UTC
Version:            (using KDE KDE 3.2.1KDE 1.2)
Installed from:    I Don't KnowRedHat RPMs

This is a feture request as per recent discussion on the kde-core-devel. 

Thread starts:
Date: Fri, 4 Feb 2005 12:00:51 +0000 (GMT)
From: Mike 'Mike' Jones <mike.jones@manchester.ac.uk>
Reply-To: kde-core-devel@kde.org
To: kde-core-devel@kde.org
Subject: slaveBase::copy between differing url hosts

Hi,

I've been writing a kio slave.  The protocol I'm implementing, gsiftp,
supports the movement of data from one URL to another URL without the data
passing through the client machine, so-called third party file transfer.

I'm using KDE 3.1.4 and have overloaded the slaveBase::copy function so
that at this stage it alerts me to the fact that it has been called.

When I drag and drop between two Konqueror windows pointing to two
differing sites the copy routine is never called, instead both get and
put are called (which, contrary to all the documentation I can find,
should only happen if copy is not implemented).

I noticed a post to this list in 2000 which states that KIO::fileCopyJob
handles this, could it be that KIO::fileCopyJob assumes that copy cannot
take place between two differing remote virtual filesystems?  If so, is it
possible to change this behaviour, or is there a straight forward
workaround I could try?

Thanks,
Mike

--
http://www.sve.man.ac.uk/General/Staff/jonesM/
Comment 1 Nate Graham 2018-04-16 18:48:25 UTC
Is this still an issue with KDE Frameworks 5.45 or greater?
Comment 2 Andrew Crouthamel 2018-09-28 03:39:25 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Nate Graham 2018-09-28 18:29:26 UTC
Yes, this is still a problem. Unfortunately it's a very deep architectural assumption of KIO. See also Bug 302448.
Comment 4 Nate Graham 2018-09-28 18:30:05 UTC
*** Bug 302448 has been marked as a duplicate of this bug. ***
Comment 5 Nate Graham 2018-09-28 18:30:08 UTC
*** Bug 307693 has been marked as a duplicate of this bug. ***
Comment 6 Nate Graham 2020-01-31 17:36:17 UTC
This should be fixable with the new kio-fuse stuff. When moving from one share to another, KIO could translate the share paths for one or both shares into a mounted FUSE URL, which allow direct copying in the way that you can't copy from one ioslave to another.
Comment 7 Nate Graham 2020-02-21 16:14:39 UTC
Specifically what I mean is that we could have KIO detect this condition and perform the copy using the FUSE mount backends for one or both of the servers.
Comment 8 a.saoutkin 2020-03-30 17:47:11 UTC
I'm not entirely sure how KIOFuse would help here.

According to the bug report, copy is not being used in this case, and instead get/put are being used. The same behaviour would occur with KIOFuse (under the hood).
Comment 9 Patrick Silva 2021-01-12 22:32:28 UTC
Still an issue.
Furthermore, Dolphin displays an inaccurate inline error message when data moving fails saying "Could not RENAME file smb:/hostname/share/folder".

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.20.80
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2