Summary: | Trying to overwrite a file with a corrupted file deletes the former | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | Safa Alfulaij <safa1996alfulaij> |
Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | andrew.crouthamel, elvis.angelaccio, nate |
Priority: | NOR | ||
Version: | 18.08.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Safa Alfulaij
2018-09-06 20:00:50 UTC
If you were using copy + paste, the source file is untouched. I would not attribute the loss of the file from CHKDSK on Windows, to Dolphin. (In reply to Andrew Crouthamel from comment #1) > If you were using copy + paste, the source file is untouched. I would not > attribute the loss of the file from CHKDSK on Windows, to Dolphin. The idea is that I'm overwriting the original file, with a corrupted file. At the end of the copy process, the original file is deleted and the corrupted (new) file couldn't be copied. I will try again and check to see if the source file is really untouched in this case. > At the end of the copy process, the original file is deleted and the > corrupted (new) file couldn't be copied I think this has the same root cause and fix as 125102. A fellow tried to submit a patch to fix that with https://phabricator.kde.org/D10663, but it didn't end up working out. Would you like to try your hand at it, Safa? You seem like a pretty capable fellow. :) *** This bug has been marked as a duplicate of bug 125102 *** |