Registered Member
|
The problems are different but for all I know related, so I'll mention them both here.
To start with I can ssh fine using the command line. I have a couple of dozen hosts configured in my ~/.ssh/config file and I've tested each one independent of dolphin/krusader. Distro: Arch Plasma: 5.9 kio: 5.31 kio-extras (fish): 16.12 dolphin: 16.12 Ok, so let's start with fish. The basic problems seems to be that fish is getting some info from my config file, but not everything. Consider this entry in my ~/.ssh/config:
"maint" is not tied into my DNS or in my hosts file, but if I put "fish://ec2-user@maint" into dolphin's address bar it works fine, so I know fish is pulling from the ~/.ssh/config file. Notice that URI however. I put the username in. I shouldn't have to do that as the username is in the config file entry, but if I try "fish://maint" it does not work. I receive: "Could not connect to host maint" The sftp kio slave gets a little farther. It will work with "sftp://maint". It connects and shows me the remote file system. This is great, except that "maint" is really just a jump host for getting into my private network. Consider another entry from my ~/.ssh/config:
If I try "sftp://test1", it fails. For what it's worth, midnightcommander on the same machine can connect using fish both to "maint" and "test1". I know, I know; there's no shared code there with the kio slave, but it does at least show that the fundamental things like ssh and the remote server are not the roadblocks. I've tried to use kdebugsettings, kdebugdialog, and kdebugdialog5 to get the kio slave to output more log messages, but no luck. no changes I made with those utilities got the fish kio slave to spit out any useful information. Any ideas? Thanks! |
Registered Member
|
Looks like this problem came back. After a couple of clicks, it just hangs.
|
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]