fish:// no longer works

el_Salmon · Posted: Tue Sep 04, 2007 9:34 am Post subject:

I have the same problem in amd64 :-(

and my Gentoo installation is new (only a week)

dracula1985 · Posted: Fri Sep 07, 2007 10:41 am Post subject:

Same problem for me, kde-3.5.7 ~amd64 on kernel 2.6.22-gentoo-r5.

using KDE_FORK_SLAVES=true konqueror fish works giving this output:

kanttu · n00b Joined: 31 Aug 2005 Posts: 58

For some reason removing stuff from ~/.ssh/known_hosts helped me, even without any other "hacks" like that fork thing.

However fish seems to be a bit laggy now

_________________
AMD Athlon64 3500+
ASUS A8N-SLI deluxe
PNY GeForce 6800GT

dracula1985 · Posted: Fri Sep 07, 2007 3:35 pm Post subject:

quag7 · Posted: Tue Oct 09, 2007 6:05 pm Post subject:

Are people still having this problem? It's kind of a shame, really, as it makes Quanta+ a lot less useful. None of the solutions mentioned here have worked, and what's most infuriating, is the fairly imprecise error ("died unexpectedly") that I am getting.
_________________
http://www.dataswamp.net

yngwin · Posted: Tue Oct 09, 2007 11:05 pm Post subject:

I find that sftp:// works as well as fish:// for my purposes.
_________________
"Those who deny freedom to others deserve it not for themselves." - Abraham Lincoln
Free Culture | Defective by Design | EFF

quag7 · Posted: Wed Oct 10, 2007 12:02 am Post subject:

Indeed. Does the job for me as well.

Thanks!

-Quag7
_________________
http://www.dataswamp.net

dracula1985 · Posted: Wed Oct 10, 2007 7:19 am Post subject:

Yes, also for me sftp:// works exactly like fish://, without having to prepend "KDE_FORK_SLAVES=true" when I start programs...
_________________
Marco

"Man is least himself when he talks in his own person. Give him a mask, and he will tell you the truth." --Oscar Wilde.

JensDittrich · n00b Joined: 19 Oct 2007 Posts: 2

If I call KDE_FORK_SLAVES=true konqueror directly in bash fish will work. If I make an alias konqi="KDE_FORK_SLAVES=true konqueror" it is broken...strange.

Greez

drizzt · Guru Joined: 21 Jul 2002 Posts: 428

Ok, today it hit me.
My fish:// worked until two or three days ago.

my program versions:

yngwin · Posted: Sun Nov 11, 2007 6:24 pm Post subject:

drizzt · Guru Joined: 21 Jul 2002 Posts: 428

Thnx for the tip,
although switching to sftp:// only works for quanta, not for konqueror

.
it still needs sorting out....
_________________
People don't have to earn my respect. I offer my respect to them, but be careful to lose my respect...

yngwin · Posted: Sun Nov 11, 2007 6:31 pm Post subject:

huh? works fine here in all kde programs, including konqueror!
_________________
"Those who deny freedom to others deserve it not for themselves." - Abraham Lincoln
Free Culture | Defective by Design | EFF

drizzt · Guru Joined: 21 Jul 2002 Posts: 428

Just as I read your post I tried again with sftp:// and it worked. :?:

Now I'm embarrassed... :oops:

Before I just got no loginrequest but a login failed message...

Anyway, thnx for your help. Now KDE is fully usable again...
_________________
People don't have to earn my respect. I offer my respect to them, but be careful to lose my respect...

Alan Turing · Posted: Wed Mar 19, 2008 1:03 pm Post subject:

I had a similar problem for a long time.
When using fish:// I often got this "protocol died unexpectedly" error message.

It seems like reemerging kdelibs after each kernel update solved the problem for me.

Alan Turing · Posted: Mon Mar 24, 2008 3:02 pm Post subject:

Oh, I'm sorry. That was not the problem.

After I updated all my packages and used prelinking (prelink -amR) konqueror with fish:// doesn't work reliable any more.
So I emerged kdelibs again and it worked perfectly.
Today I used prelinking once more and after rebooting I had the same problem again.

So actually I think that prelinking is the reason for my problems.

ova · Posted: Tue May 13, 2008 11:35 am Post subject:

Just for record: upstream is aware about fish issue and seems that it'll never be fixed:

http://bugs.kde.org/show_bug.cgi?id=145123#c73

Plague.CZ · n00b Joined: 13 Mar 2007 Posts: 72

Wow, I noticed this fish:// problem on my friend's box and laughed at him. Yesterday I connected nicely (KDE 3.5.9, kernel 2.6.23), today "protocol died unexpectedly" on SERVER1, but not on SERVER2!!!!! Then i closed the connection and no server works!!! Now common, this can't be due to kernel or KDE version when it occurs in five minutes!

thom_raindog · Guru Joined: 16 May 2008 Posts: 400

And yes.. the bug still exists, at least here.
Makes me wonder..

At least sftp does work, which is fine with me, seems to function as well for transfering my backups..

freifunk_connewitz · Apprentice Joined: 08 Feb 2006 Posts: 231

henri · Posted: Fri May 15, 2009 9:03 am Post subject:

Hi folks,

I have this problem since years from time to time.

My solution ALWAYS is to reboot the client computer. - After a reboot it almost always works again.
Logging off and on again doesn't do it for me, but a reboot does.

I know this is not a real solution but I'm simply too lazy to debug this topic because it only happens from time to time to me.

Maybe simply rebooting solves it for you, too?

Yours Henri

Mathijs · n00b Joined: 25 Sep 2007 Posts: 29

Hm that feels like solving a windows problem, and because i have this problem like every day at the moment, i would like it solved at the cause.

I am going to update my kde first to 4 and see if this still happens.
This problem did arise for me after a world update a week ago, and i did not change my kernel.
Trying to solve this every day.

Starting konqueror with KDE_FORK_SLAVES=true lets me fish, but when i want to edit a file it gives me the same error again as the editor is started without the KDE_FORK_SLAVES=true, so that is not usable either.
Restarting my session works for some time but that is a pain in the arse of course!

Using sftp:// works perfectly but that is not always usable.

toralf · Posted: Tue Aug 04, 2009 9:11 am Post subject: