there's a strange bug in KDE 4.3, up to RC3 so far, that doesn't seem to affect all users. most importantly, developers who are trying to solve the problem are not able to reproduce it, while several users have confirmed the bug & submitted debug and trace output. you find it here in the bug tracker: https://bugs.kde.org/show_bug.cgi?id=189235

if affected by this bug, fish:// protocol doesn't work in konqueror or other KDE 4.3 applications, resulting in a "connection to host xxx is broken" message.

since it can't be reproduced by everyone, but very consistently by those who get hit by it, i would like to know for whom fish:// works under KDE 4.3 and for whom it doesn't. perhaps that would provide a clue what particular configuration causes it?

--------------
i'm using KDE 4 since it's pre-alpha stage as my working environment on opensuse 11.1, everthing installed from opensuse's repositories & build service. i've got both, KDE 4.3 & 3.5 running and updated, and this bug affects only 4.3. KDE 3.5 apps connect fine via fish://, even if run from within a 4.3 session.

i noticed it first in the beginning of april 2009, when KDE 4.3 moved into beta, i believe. from 21 may onwards other reports started to confirm the bug, but strangely developers weren't able to reproduce it.


phani.

After upgrading to KDE 4.2.98 (KDE 4.3 RC3) my Kubuntu Jaunty, kio_fish doesn't work 95% of times. For example:

~# kate fish://user@myserver/etc/hosts

It just gets the file a few times, usually I get an error

Prior to KDE 4.2.98 it occured sometimes (now always). Never problems with KDE 3.X.

I'll continue with technical details in the bug report.

Although I suffer from fish connection problems, I cannot seem to reproduce when I actually try to do it under controlled conditions. I therefore suspect the issue is caused by another app (maybe not even a KDE app) running in the background, or some other unexpected situation. If I manage to reproduce in a controlled fashion then I will mention what else was running on my system. Also, it might be that the bug only affects the non-debug packages, as I recently installed the debug packages (Kubuntu) and I cannot now reproduce.

nah, isn't the debug packages. i and others who reported to the bug tracker have these installed, and it doesn't solve the problem.

at one point it was reported that dis- and then enabling nepomuk solved the problem, and at first i believed this to be true. unfortunately that's also not correct. after dis- and enabling nepomuk i can connect to a remote server, but trying to copy anything but tiny files brings up the same error again.

the bug is being discussed in a konqueror thread, but i believe it's not konqueror, but the underlying kio_slave (or whatever the package's name), since other KDE 4 apps like kate, kwrite are also affected.

seems to be a real mystery, and if you can figure out which configuration triggers the problem for you, that would be great--i can't find any way to not trigger it, unfortunately.

I would suggest everyone to drop fish:// and use sftp:// when possible. fish is mostly a hack, and should not be used.

So how about using sftp:// internally whenever someone types fish://?

If it is not supposed to be used, this would at least maintain some sort of compatibility with older versions...

IMHO we can't release kde4.3 with this bug! Or we change the remote folder from fish to sftp protocol.

einar wrote:I would suggest everyone to drop fish:// and use sftp:// when possible. fish is mostly a hack, and should not be used.

in my experience fish is much faster working with several small files: copying, editing, whatever. ftp / sftp is faster transferring large files, but the overhead, once a connection is established, to open another one seems less using fish.

i'm still using fish:// via KDE 3.5 applications, and hack or not, it works great for me.

Same problem with fish in KDE 4.3.0 (Kubuntu 9.04)

I also experience problems with large files. Connecting and copying smaller files works fine.

I built KDE 4.3 from Gentoo Portage and just copied a 600 MB file over fish://. No oddities whatsoever. Auth was kerberos.

Hello.

Same problem since I've upgraded Kubuntu 9.04 with kubuntu-ppa/backports.

I've noticed that it works better with small files, but not always.
Works perfectly with sftp.

Stupid question: what is the difference between fish and sftp ? I thought it was the same things ?!

Good luck (and thanks) for debugging !