Dolphin fails sftp copy (mostly on finish)

Support Network
1

Often when copying a file is very close to being finished (approx 50 kB remaining), dolphin stops and reports the error “File <remote File> cannot be read.” (translated from German).
If I stop the copy and try to restart, it reproducibly fails with this error message.
The error is obviously wrong, if I do so much as rename the *.part file the copy can start again.

2

Hi @Richardk2n,

All I can think of to recommend is checking that the source is OK. As in the disk it’s copying from.

2 Likes
3

Three things can happen

  1. the file is damaged
  2. the connection has timed out
  3. not enough space on the target

I don’t normally use dolphin - but for verifying this

  • I launched dolphin
  • hit Ctrl+o
  • input sftp://server/path
  • copy a 3.4G iso to the remote service
  • finish without any hickups

Using

  • Unstable branch
  • Plasma 6.3.3
  • Dolphin 24.12.3
4

@Mirdarthos The source is probably in bad shape, but the issue is more pronounced on one of my computers, so there must be something wrong on the other end as well.

@linux-aarhus Thanks for trying.
I know 1. and 3. is not the case.
I do not know the timeout, but once I have reached the reproducible state, the error is instant.

I should have specified that I copy from the remote to local disk. The files are around 40 MiB to 900 MiB.
It is not fully reproducible. The copy only refuses to start again if it stops shortly before finishing. The first stop might be a timeout. The rest I think is another issue.
I might have found a way to make it reproducible (could you please try?):

  1. Get the file onto your local disk.
  2. Remove a few KB (I just did 0.2 MiB; around 0.5 % of the file size) using truncate.
  3. Rename the file to *.part
  4. Try to copy down the file
  5. Dolphin should download the remainging few KB, but errors about the remote file instead.
5

But you have deliberately damaged the file and a .part file may have a special meaning to dolpin.

This is an edge case - I won’t use more time on this.

If you believe it is a real issue - not just constructed - I encourage you to open an issue at the KDE bugtracker at https://bugs.kde.org

6

The *.part has special meaning. During copy a *.part file is created storing the current progress, if the copy should abort, it can be continued at that point.
Meaning with truncating and renaming I can coax dolphin into “continuing” the copy from a nearly complete file, which seems to be an issue.

It happens to me every around 5 files organically, so it definitely is not constructed.
The construction is trying to make it reproducible.

I will report it to KDE.

7

Bad Ethernet adapter or bad Cat 5 cable?

1 Like