I'm not able to copy a file for an sftp session via right mouse click -> "Copy To" I do get a pop window "cannot write to <snip>" If I show the content of the remote location I do get in .xsession-errors : ... log_kio_sftp: file system free space of QUrl("sftp://<snip>@www.zwiebeltoralf.de/public_html") log_kio_sftp: username= "<snip>" , host= "www.zwiebeltoralf.de" , port= 22 log_kio_sftp: checking cache: info.username = "<snip>" , info.url = "sftp://<snip>@www.zwiebeltoralf.de" log_kio_sftp: Creating the SSH session and setting options log_kio_sftp: Trying to connect to the SSH server log_kio_sftp: Getting the SSH server hash log_kio_sftp: Checking if the SSH server is known log_kio_sftp: Trying to authenticate with the server log_kio_sftp: Trying to authenticate with public key log_kio_sftp: Trying to authenticate with password log_kio_sftp: Trying to request the sftp session log_kio_sftp: Trying to initialize the sftp session log_kio_sftp: connected ? true username: old= "<snip>" new= "<snip>" log_kio_sftp: url = QUrl("sftp://<snip>@www.zwiebeltoralf.de/public_html") - err= 0 fileSystemFreeSpace() did not call finished() or error()! Please fix the KIO slave. What works is to mark a file, copy it - then switch window and paste 1 file into the sftp target lcoation. But after 3 or 4 copies I do get an error and has to restart dolphin to continue with the next files. Reproducible: Always
I am getting the same error. I think we might have the same bug, even if the symptoms are different. See my bug #364677. It just hangs when I navigate more than four clicks on a remote system. But if I open file -> new window, I can get four more clicks before it hanging. fileSystemFreeSpace() did not call finished() or error()! Please fix the KIO slave. If I leave the window open it just keeps printing: log_kio_sftp: special(): polling
Note, if I open Kate and do a File->Open sftp://servername/some/dir then just click around ,it's also using kio_sftp and I don't get the same hang as what I get with dolphin clicking around the various directories (about 3-4 at a time, before it freezes)
And whilst I have here an ugly work around (killing all dolphin processes, starting it, having a bookmark with the remote target dir to avoid too much cd operations at the remote site, copying juts 1 file at once) - but that's awefully.
Moving to kio-extras where kio_sftp belongs.
Nudge. Cause all other kio sftp functions work fine with kde apps. It seems to be just dolphin.
I don't know if this is the same issue, but it may well be. My system log is getting spammed every few seconds with the following line: kdeinit5[19264]: log_kio_sftp: special(): polling I don't have any active SFTP connection right now, but Dolphin seems to have some dead sockets: sftp.so [kdeinit5] sftp local:/run/user/1000/klauncherTJ2531.1.slave-socket local:/run/user/1000/dolphinwX8815.8.slave-socket ... When I kill those sftp processes, I suddenly get a credentials window for a connection I used hours ago (I remember that I needed to try several times, because some connection attempts simply didn't return). Not sure if this is a Dolphin or KIO issue. Using KDE 5.9, kio kio 5.31.0 on Arch Linux
(In reply to Janek Bevendorff from comment #6) > When I kill those sftp processes, I suddenly get a credentials window for a > connection I used hours ago (I remember that I needed to try several times, In the mean while those dead processes appear again and again, bothering me with the credential windeow again and again until I kill all dolphin and sftp.so processes at once. So even in 17.04.3 this feature is completely b0rked here.
Let's keep out the ranting, can we? That is not helpful and just demotivating for the devs who want to work on it.
I realized yesterday that the issue vanished at this Gentoo Linux desktop. The relevant changes made in the past are (AFAICT): - switch consolekit->elogind - linux kernel 4.12.4->5 - kde-plasma/plasma-workspace-5.10.4-r1->r2 Furthermore I re-emerged eudev package, kde-frameworks/kfilemetadata-5.34.0 and kde-apps/kio-extras-17.04.3. FWIW - bug #370370 is a dup, isn't it ?
(In reply to Toralf Förster from comment #9) > I realized yesterday that the issue vanished at this Gentoo Linux desktop. > > The relevant changes made in the past are (AFAICT): > - switch consolekit->elogind > - linux kernel 4.12.4->5 > - kde-plasma/plasma-workspace-5.10.4-r1->r2 > > Furthermore I re-emerged eudev package, kde-frameworks/kfilemetadata-5.34.0 > and kde-apps/kio-extras-17.04.3. > > FWIW - bug #370370 is a dup, isn't it ? umpf, forget comment #9 - for some reasosn I missed the "s" in sftp, and just the common ftp made no problems.
I'm guessing the original issue is no longer reproducible by anyone on the 19.12 release? Should it be: which version of libssh do you use?
(In reply to Harald Sitter from comment #11) > I'm guessing the original issue is no longer reproducible by anyone on the > 19.12 release? > Should it be: which version of libssh do you use? net-libs/libssh-0.9.3 net-libs/libssh2-1.9.0_p20190913 stable Gentoo KDE desktop LibreSSL The issue is still rpesent - I cannot open a FTP session via KDE, no problems at the command line.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!