KDED Password Module is not running before using ftp, and launched when I go to my ftp server, so everything seems ok for it.

Can you reproduce the issue under a new user?

I have the same problem in kde 4.3.4 with kubuntu.
The server warn me that too many connections. However I have no problem with filezilla.
How can I see how many connections does dolphin? (In my case is dolphin)

You can use System Activity ( accessible through Ctrl + Esc, or the 2nd icon from the left in KRunner ) to filter by kio_ftp. The number of instances of kio_ftp represents the number of connections made to FTP servers by KIO.

I am having the same problem. kio_ftp maxinstances=2, but the System Activity monitor shows many more. Starting up an FTP connection in Dolphin automatically starts 4 instances of kio_ftp, and then every file I open (php, png, txt, etc.) is an additional connection. The biggest problem though is that when I close the files I have opened the kio_ftp instance sticks around, so after editing just a couple files I am at my maximum allowed connections. This is really affecting my productivity, please help!

Please file a bug at bugs.kde.org.

It's a old wish:
https://bugs.kde.org/show_bug.cgi?id=64647

I found a work around for this . I am using the Plasma Desktop, and if you assign a "Folder View" gadget a ftp path you can browse your ftp, open/edit/save/download/upload files and do so all without violating maxinstances variable.

Sorry for answering so late, I was quite busy last days.
I've upgraded to kde 4.4 RC2 and I still have the problem (even with only browsing my files throught Dolphin). I have several kio_ftp process running (8 !).

Should I create a new bug as there is already one similar in wish list, as mentioned above ?

EDIT: tryed with an other user (new one), as asked, same thing.

Filing a new bug will not help likely.

This bug is caused because by default KIO does not "schedule" "jobs". Each interaction with a file, whether it is moving, deleting, stating ( checking size and existance ) etc. is represented and controlled through a "job".

The limits are only applied if the job is "scheduled". Patches that change to scheduling by default cannot occur as more advanced jobs such as copying could cause deadlocks if the limits were set to 1 ( since the file needs to be both read from and written in another location, which isn't possible ).

bcooksley wrote:Filing a new bug will not help likely.

This bug is caused because by default KIO does not "schedule" "jobs". Each interaction with a file, whether it is moving, deleting, stating ( checking size and existance ) etc. is represented and controlled through a "job".

The limits are only applied if the job is "scheduled". Patches that change to scheduling by default cannot occur as more advanced jobs such as copying could cause deadlocks if the limits were set to 1 ( since the file needs to be both read from and written in another location, which isn't possible ).

We can't set a minimum limit of 2 ?
It's a pity because Kde and Konqueror/Dolphin are from far the more handy tools for me to use ftp (with console ftp), but I can't use them with the ftp of my server because of this.

Anyway, thanks for answering.

Unfortunately unless the job is scheduled, it is up to the application to limit itself, which simply doesn't happen.

I don't understand why the schedule is not possible with a minimum limit of 2 ? Sorry if the question is silly

I think the problem was if two jobs which required more than 1 operation were started at the same time, then the dead lock would happen then as well.

Ok, thanks for the details.