Bug 284081

Summary:	dolphin freezes transfering lage files on smb protocol
Product:	[Frameworks and Libraries] kio	Reporter:	pier andre <pier_andreit>
Component:	smb	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	adawit
Priority:	NOR
Version:	4.7
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:

Description pier andre 2011-10-15 12:00:58 UTC

Version:           1.7 (using KDE 4.7.2) 
OS:                Linux

I want to confirm this bug, using kde 4.7.2 with opensuse tumbleweed
64bit. if I transfer large files (10 movies 0.7GB each) using sftp://...
protocol under dolphin, transfere starts, but if, after the transfere is
started, I try to change directory dolphin freezes for minutes, in practice
during transfering dolphin is unusable in that sftp://, if I use konqueror it
doesn't happen.
I would like to point light on this bug that is very ugly.

Reproducible: Always

Steps to Reproduce:
1)write in the address bar of dolphin sftp://IPaddressofsftpsite and press return
2)open another tab at /home/user
3)drag and drop (copy or move) large files (10 movies 0.7GB each)from sftp://... to /home..
4)goto sftp:// and change directory, dolphin freezes



Actual Results:  
dolphin freezes

Expected Results:  
show the files in the new directory

Comment 1 Peter Penz 2011-10-15 12:27:59 UTC

Thanks for the report. Konqueror uses the Dolphin-engine internally, so I'm surprised that this does not happen in Konqueror too. Could it be that you tried to transfer the files with Konqueror after Dolphin was frozen? Can you reproduce this kind of issue each time or did it happen "only" once?

Comment 2 pier andre 2011-10-15 15:53:36 UTC

sorry, I made an error, the protocol was smb:// not sftp://, I just tried now, konqueror is only slow, dolphin or is very slow or freeze

Comment 3 Peter Penz 2011-10-15 18:22:00 UTC

ok, thanks for the update!

Comment 4 Dawit Alemayehu 2011-11-06 07:26:25 UTC


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