Bug 233526

Summary:	accessing ftp folders results too many connections error
Product:	[Unmaintained] kio	Reporter:	Viesturs Zarins <viesturs.zarins>
Component:	ftp	Assignee:	David Faure <faure>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	adawit, finex
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Viesturs Zarins 2010-04-06 19:24:09 UTC

Version:           1.4 (using 4.4.2 %28KDE 4.4.2%29%2C Arch Linux)
Compiler:          gcc
OS:                Linux %28i686%29 release 2.6.32-ARCH

Steps to reproduce:

go to ftp site, that has an max connection limit (most likely any non-anonymous ftp will do).
I have a site with the limit set to max 3 connections.

Type ftp site addres in dolphin adress bar, enter username password, set to remember un KWallet.

Try to browse into a subfolder and paste a file into the folder. The following error appears:

"530 Sorry, the maximum number of clients (3) from your host are already connected."

Comment 1 FiNeX 2010-08-01 15:41:16 UTC

I can confirm this bug on KDE SC 4.4.5 too. Probably this is a KIO:FTP bug: I can reproduce it with konqueror too.

Comment 2 Dawit Alemayehu 2011-03-15 19:51:08 UTC

Do you still see this problem ? It should no longer be the case with KDE v4.5 and up.

Comment 3 FiNeX 2011-03-16 18:30:55 UTC

A first test with 4.6 looks fine, but I would leave this open for a couple of months for some more tests. Thanks :-)

Comment 4 Dawit Alemayehu 2011-03-17 15:57:38 UTC

(In reply to comment #3)
> A first test with 4.6 looks fine, but I would leave this open for a couple of
> months for some more tests. Thanks :-)

The issue is not in this ioslave, but the process that manages it, KIO::Scheduler and that was fixed in KDE v4.5. See comment#1 in bug 243206 for the details. IOW, it has already been more than few months for this to be tested. :) Besides one can always reopen the ticket if they still have problems. Marking this as duplicate.

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