fish:// broken after upgrade to 12.1
Hi
I regularly use fish:// from konqueror and kate for remote access and editing. After upgrading from 12.0 to 12.1 i permanently get: An error occurred while loading fish://aunty@192.168.0.4: The process for the fish://192.168.0.4 protocol died unexpectedly. when trying to connect from the upgraded machine. It doesn't make any difference if i try to connect as a different user, or to a different machine. When I sit at one of the other machines - which are still running 12.0 - i can connect to the 12.1 box perfectly well, as well as to other 12.0 machines. any clues much appreciated, aunty |
You can try to comment all lines in ~/.ssh/known_hosts file.
|
nahh it's not that. i can do a normal ssh shell login from the 12.1 machine without any problems.
|
It's not really an answer to your question, but sshfs (available at slackbuilds.org) should allow you to achieve the same goal.
Brian |
thanx for that brian. just got back to it. the sshfs works beautifully - .tgz available at linuxpackages.
fish:// still not working tho . . . odd !! aunty |
I'm no expert with fish, but what happens when you try fish://localhost?
Are you running the remote ssh daemon on a non-standard port? |
Ahh . . good thought, but alas . . .
An error occurred while loading fish://localhost:also, am using standard ports for everything. |
is it slackware 12.1 stable or current version
I upgraded slackware 10.0 to 12.1 (stable) and fish:// in konqueror works here... I deleted the old ~/.kde dir from 10.0 though (my /home is on separate partition so .kde was still here after the upgrade) |
Im using 12.1 fully patched and fish works here. However, looks like this is a common problem for some folks:
http://bugs.kde.org/show_bug.cgi?id=145123 Just some more jabs in the dark: 1. Exit KDE/X and delete all ~/.DCOPserver* files. 2. Empty ~/.ICEauthority and ~.Xauthority (cat /dev/null > .ICEauthority) 3. While not in KDE/X, delete the cache files: ~/.kde/cache-$HOSTNAME/ksycoca 4. Temporarily rename ~/.kde to ~/.kde-old and then start KDE. This should expose whether the problem is related to your KDE settings. One person suggested a work-around of setting the environment variable KDE_FORK_SLAVES=true. |
I'm using 12.1 upgraded from 12.0 and fully patched, and fish isn't working for me. I didn't delete .kde though, so that's probably the problem. Since I'm not interested in fish at this moment I won't bother deleting or moving ~/.kde, but I will say that launching konqueror with
Code:
$ KDE_FORK_SLAVES=true konqueror & |
Curiouser and curiouser. The fish protocol works for me (12.1/3.5.9) and I do not have the KDE_FORK_SLAVES environment variable set on my box.
|
All times are GMT -5. The time now is 12:51 PM. |