Bug 502419 - More robust duplicate detection when overwriting file
Summary: More robust duplicate detection when overwriting file
Status: RESOLVED DUPLICATE of bug 337277
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 24.12.3
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-04-04 18:52 UTC by Alexander Wilms
Modified: 2025-04-12 18:49 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Wilms 2025-04-04 18:52:38 UTC
SUMMARY
When copying/moving a file to a path where a file with the same name exists, a dialog is shown stating that the files seem identical with the following tooltip:

"The files are likely to be identical: They have the same size and their contents are the same at the beginning, middle and end"

Perhaps this could be more robust.

STEPS TO REPRODUCE
1. Copy a file to a path where another copy already exists.

OBSERVED RESULT
A dialog stating the following:
"The files are likely to be identical: They have the same size and their contents are the same at the beginning, middle and end"

EXPECTED RESULT
I'd expect that a robust method is used to ensure one doesn't accidentally overwrite a file if it is different. I don't know how big the portions are which are being compared, but maybe a SHA checksum would reduce the likelihood of collisions.
The "Checksums" tab of the properties dialog already integrates various checksums, so that could be adapted.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20250329
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.13.8-1-default (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
Comment 1 John Kizer 2025-04-12 18:49:08 UTC
Hi - merging this in with an existing feature request for this topic. Thanks!

*** This bug has been marked as a duplicate of bug 337277 ***