[fish] failed move to SSH server via fish panel deletes original file #3963
Labels
area: vfs
Virtual File System support
prio: high
Serious problem that could block progress
ver: 4.8.22
Reproducible in version 4.8.22
Important
This issue was migrated from Trac:
andvaranaut
(jm.lopez@….com)howaboutsynergy@….me
Description of the problem:
When moving files over SSH to a server using fish, if an I/O error is reported in the operation, the original file is deleted regardless of what the option chosen in the dialog is.
In particular, if you are using a non-root user and try to write in a privileged path, a "Cannot chmod target file" error is triggered (I/O error 121). If you choose Retry, the same dialog reappears; if you choose Skip, Skip all or Abort, the original file is deleted even though the move was unsuccessful.
The end result is that Midnight Commander deletes files without being asked to (and with no way to cancel the operation).
The bug is present both in the version packaged in my distro (4.8.18) and the current stable one (4.8.22). I have compiled it from source to test it out.
I'm rather sure that this is another facet of #3961. I'm opening a new ticket because a) it's a more generic problem (any I/O error might seemingly trigger the bug) and b) I have checked that it is still present in the current version, as requested by the bug reporting page.
Steps to reproduce:
Obtained Result
An I/O error dialog (error 121) comes up complaining that the remote chown of the file failed. If you choose Retry, the dialog comes up again. Choosing any option other than Retry deletes the original file.
Expected Result
Choosing any option other than Retry in the I/O error dialog should preserve the original file.
Result of mc -V:
Result of mc -F:
mc --configure-options is empty (I used a plain configure/make).
Thanks for your help!
The text was updated successfully, but these errors were encountered: