Bug 183594 - fish stalls when transferring large quantities of data
Summary: fish stalls when transferring large quantities of data
Status: RESOLVED DUPLICATE of bug 147948
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: fish (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Jörg Walter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-07 19:56 UTC by doc.evans
Modified: 2010-08-04 10:23 UTC (History)
3 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 doc.evans 2009-02-07 19:56:26 UTC
Version:            (using KDE 4.1.4)
OS:                Linux
Installed from:    Ubuntu Packages

Transferring a file hierarchy of about 22GB over Ethernet from a Kubuntu 8.04 system to a Kubunutu 8.10 system, fish always fails after a few minutes.

I am using fish on the 8.10 (KDE 4.1.4) end of the link to pull the files.

After a while (typically approx 1GB), the transfer completely stalls and has to be cancelled (looking at the network interfaces shows that no packets are flowing).

The transfer works fine all the way to completeion if I use scp from the command line instead of fish.
Comment 1 FiNeX 2009-02-08 19:54:48 UTC
does it happens even using dolphin?
Comment 2 Frank Sagurna 2009-02-10 18:59:42 UTC
I can confirm this here for kde 4.2 on kubuntu intrepid. I could swear i commented on a bug report on exact that issue, and there was a patch that should have been apllied, but i cant find it anymore.
I dont know why.
Comment 3 Frank Sagurna 2009-02-10 19:03:12 UTC
Ah i found it ... i was in doubt of my brain working for a moment:
https://bugs.kde.org/show_bug.cgi?id=147948

Anyways, the bug is still there in KDE4.2
Comment 4 doc.evans 2009-03-11 23:29:38 UTC
(In reply to comment #1)
> does it happens even using dolphin?

Yes.

I just tried to transfer 60GB using fish with dolphin. The transfer halted at 1.6GB.

And I confirm that the problem exists in KDE 4.2.
Comment 5 Nicolas L. 2010-08-04 10:23:15 UTC

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