[dolphin] [Bug 492976] New: Сritical error files! With a broken file, when copying it again, it considers that the file already exists.
Dellius
bugzilla_noreply at kde.org
Wed Sep 11 11:58:10 BST 2024
https://bugs.kde.org/show_bug.cgi?id=492976
Bug ID: 492976
Summary: Сritical error files! With a broken file, when copying
it again, it considers that the file already exists.
Classification: Applications
Product: dolphin
Version: 24.08.0
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: dolphin-bugs-null at kde.org
Reporter: delliushencky at gmail.com
CC: kfm-devel at kde.org
Target Milestone: ---
***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org
If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Please remove this comment after reading and before submitting - thanks!
***
SUMMARY
A critical error. Which creates big problems when working with a large number
of files.
STEPS TO REPRODUCE
1. Start copying the file to the directory.
2. Abort, terminate, when copying a file(s) by any of the methods (for example,
the space has run out).
3. Copy the files again, when prompted to "replace", answer no. (since there
are 1000 files, for example, and only 1 is broken, we do not need to copy 1000
files again).
OBSERVED RESULT
The broken file remains as an existing one. And when deleting the original --
we get broken files -- here and there.
EXPECTED RESULT
So that when copying, I could compare files (at least compare files by size)
and when choosing "skip all", I only skipped the Same and Good Files, but
replace different sizes or better, to ask again about replacing different
files.
SOFTWARE/OS VERSIONS
Windows:
macOS:
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma:
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the kfm-devel
mailing list