https://bugs.kde.org/show_bug.cgi?id=500360
--- Comment #10 from Chris Winters <chris.wint...@coldcanuck.ca> --- Have some updated info to share. Not sure how helpful it will be, but here it goes. I decided to spin up a couple VMs to test two different configurations to see if I can at least isolate where the issue might be occurring. Both VMs are Arch Linux so all packages should be up to date. 1) Arch Linux + Plasma + Dolphin + Dolphin Plugins + Kio (and all additional packages related to kio) + Gnome-Keyring (replacing KDE Wallet/ksshaskpass completely) This configuration prevents fish protocol from connecting, and the sftp protocol exhibits the same behaviour as described in the original report. SSH Key passphrases are not saved, and the user is asked to enter the passphrase when connecting to sftp via Dolphin. 2) Arch Linux + Plasma + Thunar (probably doesn't matter, any file gvfs enabled filed manager would do) + GVFS (and all additional packages related to GVFS) + KDE Wallet + ksshaskpass This configuration works as expected. On first connection to an sftp share the user is presented with a passphrase dialogue with the option to save the passphrase. Thunar (or gvfs) will then correctly fetch the saved passphrase on subsequent connection attempts, even in a new session (after a logout or a reboot). The issue therefore seems to be with KIO. I've read somewhere that KIO does not natively support org.freedesktop.secrets (libsecret) and perhaps this is where the issue is stemming from. There is a patch available that adds support so I'm going to set up a vanilla Plasma instance and add that patch to see the results. If it works, I'll use that as an acceptable workaround. -- You are receiving this mail because: You are watching all bug changes.
