Bug 260999 - kde4 regression: cannot copy from sftp to sftp
Summary: kde4 regression: cannot copy from sftp to sftp
Status: RESOLVED DUPLICATE of bug 267135
Alias: None
Product: krusader
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Shie Erlich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-22 20:44 UTC by Stefan Endrullis
Modified: 2011-03-02 20:04 UTC (History)
2 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 Stefan Endrullis 2010-12-22 20:44:50 UTC
Version:           unspecified (using KDE 4.5.1) 
OS:                Linux

Krusader version: 2.2.0-beta1

When I try to copy a file from one sftp connection to another sftp connection (tested with 2 connections to the same host) the file is not copied to the target directory.  The file transfer progress remains at 0% and does not finish ever.

Reproducible: Always

Steps to Reproduce:
Use the left and the right side to connect to the same host via sftp.  Change at least one of the directories so that both are not equal.  Then copy a file from one side to the other.

Actual Results:  
File transfer stays at 0% and nothing is copied.

Expected Results:  
The file should be copied and we should also see a file transfer progress.
Comment 1 Florian Staudacher 2011-01-08 23:23:47 UTC
To me this does not only happen with Krusader but also in Dolphin (I guess it has to do with KIO then?)

I have the window split and drag one file from one server (using ssh user+pass) to another server (using public key+passphrase). The filetransfer remains at 0% and never finishes.
Comment 2 Stefan Endrullis 2011-01-08 23:28:10 UTC
OK, you are right.  Unfortunately, I cannot change the meta data of the bug anymore, except the title.
Comment 3 Frank Reininghaus 2011-03-02 20:04:25 UTC
I'll mark it as a duplicate of bug 267135, which appears to be about the same issue and has the correct assignee already.

*** This bug has been marked as a duplicate of bug 267135 ***