I get a "Could not write to file" when copying a directory from an MTP device that breaks inexplicably half way through. At first I thought it was a permissions issue, but it turns out it should read "could not read file", not "could not write to file". Reproducible: Always Steps to Reproduce: 1. Copy a bunch of files from an MTP device 2. Inevitably this process will die if it's an Orange phone 3. "Could not write to file" appears Actual Results: "Could not write to file" dialog Expected Results: "Could not read file" dialog.
So you were trying to copy the file to a location for which you didn't have write permission, and the wrong error message was displayed?
Nope, I had write permission for the location I was writing to, it's just that the source may have disappeared, but I got the wrong error.
Ah okay, gotcha. Dolphin's MTP support is known to be spotty, and I think it makes more sense to focus on fixing those problems than improving the error message. Here are some relevant bugs that could have caused the underlying issue: https://bugs.kde.org/show_bug.cgi?id=372860 https://bugs.kde.org/show_bug.cgi?id=379680 https://bugs.kde.org/show_bug.cgi?id=375840 Are you okay with closing this bug in favor of those?
No response... I do agree with @Nate that we should close this report and focus on the specific underlying problems (which should of course also resolve this issue).