Bug 510841 - No prompt to permanently delete file after undoing
Summary: No prompt to permanently delete file after undoing
Status: RESOLVED DUPLICATE of bug 451745
Alias: None
Product: dolphin
Classification: Applications
Component: general (other bugs)
Version First Reported In: 25.08.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-10-20 18:53 UTC by leo
Modified: 2026-01-01 14:30 UTC (History)
4 users (show)

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


Attachments
Demonstration (827.37 KB, video/webm)
2025-10-20 18:53 UTC, leo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description leo 2025-10-20 18:53:06 UTC
Created attachment 185931 [details]
Demonstration

SUMMARY
If I copy a file, permanently delete the original file, then press undo (Ctrl + Z), the copied file gets permanently deleted and the file is lost permanently

STEPS TO REPRODUCE
1. Create file/folder
2. Copy file/folder
3. Delete original file/folder
4. Press Ctrl + Z
5. Observe permanent loss of file without warning

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: CachyOS Linux
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Comment 1 Méven 2025-10-23 15:50:44 UTC
> 5. Observe permanent loss of file without warning

So the destination of the copy is removed upon copying Ctrl+z is the issue.

What would you suggest dolphin would do then ?

We could have some confirmation when undoing the copy.

A clever thing to do would be in the Copy undo logic check if the original file is still there or not, and ask then if you want to remove the destination or move the file back where it was.
This would be a bit tedious to implement.

Still this might not be a legitimate feature: Ctrl+Z is a destructive operation by nature, it can delete files and directory and that's expected.
Comment 2 leo 2025-10-23 17:45:20 UTC
> We could have some confirmation when undoing the copy.
> 
> A clever thing to do would be in the Copy undo logic check if the original
> file is still there or not, and ask then if you want to remove the
> destination or move the file back where it was.
This is what I was envisioning.
Comment 3 aristsakas 2026-01-01 14:30:36 UTC

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