Summary: | When showing "file copy/move error" message window, there should be "retry" option besides "skip" , "auto skip" and "cancel" . | ||
---|---|---|---|
Product: | [Unmaintained] kio | Reporter: | GGG <ggg_mail> |
Component: | general | Assignee: | David Faure <faure> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | adawit, amirseni, anderslund, b7.10110111, correo.cuervo, dedeibel.lists, dion, kde-bugzilla, martin.sandsmark, MurzNN, oleg.atamanenko+kde, olerass, peter.penz19, sam.albuquerque |
Priority: | NOR | ||
Version: | 4.4 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.0 | |
Sentry Crash Report: |
Description
GGG
2010-01-11 19:04:28 UTC
*** Bug 249541 has been marked as a duplicate of this bug. *** I am confirming this (see bug 249541) and rising priority; it should be easy to fix and makes this kind of failure much easier to handle. Instead of having to re-organize the whole copying process, you should be able to just retry the last failure. This is also observed in KDE4.5.1 Chances are that when the user gets such an issue, it is possible for him to fix the issue that is causing the errors(egs: if disk full; delete some unnecessary files from target). In such a scenario, a retry is a better option as it is possible for the user to easily continue the copy process rather than hunt for the file that was lost in transit. *** Bug 227415 has been marked as a duplicate of this bug. *** *** Bug 267861 has been marked as a duplicate of this bug. *** Still present in 4.9.1. And currently the message is rather useless, because the user wouldn't want to lose the file because dolphin couldn't read it. The only sensible thing to do currently is Cancel, remove all already copied files and retry all over again. *** Bug 312555 has been marked as a duplicate of this bug. *** Still present in 4.10.2 Retry and Cancel are more sensible options when disk is full, Autoskip and skip are not productive options. *** Bug 232543 has been marked as a duplicate of this bug. *** *** Bug 155815 has been marked as a duplicate of this bug. *** Wonderful! Thans a lot :) Anders, the commit was made in the frameworks branch, so do not expect it soon. *** Bug 328710 has been marked as a duplicate of this bug. *** |