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.

Is there a way to make that a full-fledged bug and not a wish, since it is a genuine interoperability problem?

I would suggest contacting the maintainer of KIO, dfaure in #kde-devel regarding such questions.

Hmm, I'm having this problem too. Something that doesn't seem to have been mentioned is that it doesn't seem like these connections close themselves properly ... I would expect the sessions to close themselves properly ... but they don't seem to. This can lead to it saying "too many connections" when I have nothing open and then try to open something (ie: Dolphin, Kate) and get a too many connections right off the bat.

dwidmann wrote:Hmm, I'm having this problem too. Something that doesn't seem to have been mentioned is that it doesn't seem like these connections close themselves properly ... I would expect the sessions to close themselves properly ... but they don't seem to. This can lead to it saying "too many connections" when I have nothing open and then try to open something (ie: Dolphin, Kate) and get a too many connections right off the bat.

I'm having this problem too, for a long time. I also filled a bug report for it, but it seems to hang there forever... Connections don't close themselves after closing Dolphin,Kate... It turns out they eventually close, after 2 minutes or so. This also happens for usb pendrives, I can't unmount my pendrive untill I kill all kio_file processes, which is annoying a lot. I've found a workaround for ftp, I mount ftp server with curlftpfs and then it behaves as local disk, but it's slow like a snail.

So my question is: is somebody already working on fixing this bug (because really, it's not a wish, it's a serious bug)?

When I run into the problem, as a workaround, I run:

Code: Select all

pkill kio_ftp

This bug is a real problem to me, all my 15 allowed ftp connections are in use. Manually killing kio_ftp processes is annoying. I seriously hope that, this is fixed in KDE SC 4.5.