Hi all,
I have a remote Centos server on which I’d like to edit some files.
I can connect using SSH.
I can configure Dolphin to see files on the remote either using the fish or the sftp protocol.
Whichever of the two protocols I use, I can copy files to and from my local PC .
HOWEVER, when I try to directly edit the files on the remote PC (i.e. I double-click on a text file, which in turn opens Kate or Kwrite) Kate/Kwrite opens and then locks without even showing the contents of the remote file.
I remember having done this in the past, albeit on a different PC running a different linux distro.
What is it that is happening here?
Anybody else experiencing this?
I have now noticed that, while I have various network folders mapped in Dolphin, nothing is visible in the open dialog of Kate if I click on “Network” in the “Places” sidebar.
Am I missing some component?
Well, Dolphin is KDE4 based, while Kate/Kwrite use KF5.
Anyway, it works fine here (13.2/KDE:Frameworks5) with the KF5 based Kate/Kate as well, but then I’m already on KF 5.11. Should be in Tumbleweed soon as well though.
But check that you have kio-extras5 installed (should be by default).
And, does it work if you manually enter something like “sftp://host” into the address bar?
Also check that all network related services are enabled in systemsettings5->Background Services.
But this might also indicate a problem with kwalletd5. Kate/KWrite try to open the wallet before accessing a sftp URL, to be able to get/store the password that might be needed.
Just to be sure: it might be that it asks for a password, but the password dialog is hidden behind other windows (or on a different screen if you have more than one). So check that please.
And if you never used kwalletd5 before, it will ask whether it should migrate the KDE4 wallets. This might cause a block too until you answer it.
Otherwise it’s probably kwalletd5 that hangs.
Does it help if you kill it?
Can you reproduce the problem on a fresh user account?
Try to delete ~/.config/kwalletrc.
If you don’t have important passwords in your kwallets, you might try to delete ~/.local/share/kwalletd/ (or just rename it as a test) too.
You could additionally also delete/rename ~/.kde4/share/apps/kwallet/, to prevent possible problems caused by the migration.
No, it’s not the first time I use kwalletd5… migration was done a few weeks ago.
No, kate stays hung even after I successfully kill kwalletd5.
Moreover, I don’t see kwalletd5 restarting itself, even after killing Kate and retrying connecting.
I tried starting Kate from the cli, and got this before the hang:
cristiano@xmper8q3:~> kate
QWidget::setLayout: Attempting to set QLayout "" on KateMDI::ToolView "", which already has a layout
kf5.kservice.sycoca: Trying to open ksycoca from "/home/cristiano/.cache/ksycoca5"
org.kde.kurifilter-shorturi: "sftp://AMENDED"
org.kde.kurifilter-shorturi: path = "" isLocalFullPath= false exists= false url= QUrl( "sftp://AMENDED" )
org.kde.kurifilter-ikws: "sftp://AMENDED" : QUrl( "sftp://dvd10openrt1.dq.bkd" ) , type = 0
Not exactly. I created a new account and tried connecting from Kate. At first, I got an error because Kate (well, kio_sftp) was not able to find the server.
Than I realized that I had to configure the proxy in “Configure Desktop”. After doing that, Kate now starts connecting (I get a “busy” mouse cursor) but never finishes.
I looked around to see if there was a login dialog somewhere, but could not find it.
However, this is not the same as my primary user, as Kate is not hanging (i.e. the GUI is responsive, the windows doesn’t stop refreshing, etc). It is only indefinitely waiting.
Obviously, connecting with dolphin succeeds instantaneously.
I’d prefer not to do this, I am afraid of losing important passwords. It seems to me the problem is not related to kwallet.
However, if - after reading this - you still think I should try this, I’ll do it.
I tried to open Kate as root with kdesu, and I got yet another behavior:
first time, Kate told me the ssh fingerprint was not in his db and so asked for confirmation.
After that, Kate behaved like it had connected correctly, and it showed a progress bar (it does this when it is fetching the directory listing from a remote site), but it did not fetch anything and the progress bar stayed at 0%.
Kate however was not hung and I could cancel the dialog without problems.
Well, as you wrote in the other thread, you are behind a proxy.
And maybe that might be the actual problem (I am not, and it is working fine here), as I mentioned there too.