Created attachment 112824 [details] reporting kio bugs are disabled?! First, sorry that I am reporting KIO bug to Dolphin, but there is no possibility to create bug report for KIO directly. Why?! And now the bug: when I copy files to remote machine using sftp protocol (sftp kio) and remove machine has full disk, there is no error reported to user, but files are not copied... From shell, it is visible that copy was not successful: ``` scp file root@remote:/home/user/ ... kio_sftp(23014) sftpProtocol::sftpPut: Error during 'put'. Aborting. ... kio_sftp(23014)/kio (kioslave) KIO::SlaveBase::dispatchLoop: slave was killed, returning ``` When I am using scp command, I get usable error message: ``` scp file root@remote:/home/user scp: /home/user//file: No space left on device ``` I am using KDE from Kubuntu 18.04 packages: ``` $ kioclient --version Qt: 4.8.7 KDE Development Platform: 4.14.38 KIO Client: 2.0 ```
The category is frameworks-kio, "Kio" is the old KDE 4.x one :) sftp is in kio-extras, though, re-assigning
Oh, you *are* on 4.x, umm, but I doubt this changed a lot in 5 s I assume this is till valid
Ups. You are correct, i was using kioclient from KDE4 in console, sorry. I mixed kioclient and scp commands in original post moreover... Anyway, the same problem exists with kio 5: cd /tmp/ mkdir ramdisk sudo mount -t tmpfs - ramdisk -o size=1M dd if=/dev/urandom of=bigfile bs=1M count=2 kioclient5 cp bigfile sftp://localhost/tmp/ramdisk ... kf5.kio.core.copyjob: emit processedSize 1044480 kf5.kio.core.copyjob: d->state= 6 kf5.kio.core.copyjob: 0 files remaining kf5.kio.core.copyjob: kf5.kio.core.copyjob: copyNextFile finished kf5.kio.core.copyjob: KDirNotify'ing FilesAdded QUrl("sftp://localhost/tmp/ramdisk" echo $? 0 ls -alh ramdisk/* bigfile -rw-rw-r-- 1 karry karry 2.0M May 24 07:19 bigfile -rw-rw-r-- 1 karry karry 1.0M May 24 07:23 ramdisk/bigfile.part kioclient5 --version kioclient 5.12.4
This should be fixed for the 20.04 release with more explicit error handling introduced via https://phabricator.kde.org/D27153 That is to say: cannot reproduce on git master but can reproduce with the 19.12 release. I suspect the error was originally forgotten to be passed along somewhere. There's also bug #418443 which is kinda related as the UX for out-of-space is a bit garbage.