| Summary: | "Could not write to file" dialog on MTP actually means "could not read from device". | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | Dan Dart <kde> |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | minor | CC: | mail, nate |
| Priority: | NOR | ||
| Version First Reported In: | 15.12.3 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Dan Dart
2016-07-04 07:34:16 UTC
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). |