On Mon, 31 Dec 2018, Marvin Jones via trinity-users wrote:
I just noticed I can no longer sftp in konqueror to sites I normally "visit". It's been a week or 2 since I last used the feature, but I think a Trinity update may have caused this snafu.
I'm running Ubuntu 16.04 with Trinity 14.0.6 using the Preliminary Stable Builds repository. Still fails after a reboot on the client end. The other end involves various servers.
ssh, sftp, and sshfs all play nice from the command line.
I'll do a test that just occurred to me: I'll try sftp'ing into my ownw orkstation.
OH BOY! It just gets stranger and stranger.
One of my brain cells fired off and I remembered "fish". (And I just now see a reply from Nikolaus also about "fish".)
So, locally I tried all 'flavors' of sftp and fish. All the following done in the konqueror address "box":
|fish://jonesy@localhost (WORKS!)
|fish://jonesy@127.0.0.1 (instantly:) |An error occurred while loading fish://jonesy@127.0.0.1: |Could not connect to host 127.0.0.1.
|fish://jonesy@192.168.1.17 (instantly:) |An error occurred while loading fish://jonesy@192.168.1.17: |Could not connect to host 192.168.1.17.
|sftp://jonesy@localhost (after about 1 minute:) |An error occurred while loading sftp://jonesy@localhost: |The process for the sftp://localhost protocol died unexpectedly.
|sftp://jonesy@127.0.0.1 (after about 1 minute:) |An error occurred while loading sftp://jonesy@127.0.0.1: |The process for the sftp://127.0.0.1 protocol died unexpectedly.
|sftp://jonesy@192.168.1.17 (after about 1 minute:) |An error occurred while loading sftp://jonesy@192.168.1.17: |The process for the sftp://192.168.1.17 protocol died unexpectedly.
What's especially strange is that fish to localhost WORKS (which IS mapped to 127.0.0.1 in /etc/hosts), but fish to 127.0.0.1 FAILS!
So, the test(s) shows that problem occurs within my local workstation, and should rule out any issue with the remote hosts.
I have to believe the problem is in konqueror or some sub-component it uses for this feature/function.
How to debug?? It's not like I can use -v -v -v as I can on the ssh/sftp command line.
Jonesy