Bug 514215

Summary: Attempting to delete a file within a cryfs or gocryptfs mount creates the .Trash-1000 folder but moves the file to ~/.local/share/Trash/
Product: [Applications] dolphin Reporter: FrostBird347 <FrostBird347>
Component: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: dolphin-bugs-null, oliver.schramm97
Priority: NOR    
Version First Reported In: 25.08.1   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description FrostBird347 2026-01-06 07:33:07 UTC
SUMMARY
Attempting to delete a file within a cryfs or gocryptfs with dolphin creates the ".Trash-1000" folder but moves the file to "~/.local/share/Trash/"
With unencrypted volumes this is simply an inconvenience (and could lead to the root volume running out of space), however with encrypted volumes this risks leaking data.
I haven't tested other filesystems, but I would be surprised if no other similar projects were impacted.

STEPS TO REPRODUCE
1. Install cryfs or gocryptfs.
2. Create a new cryfs/gocryptfs volume and mount it to a local folder within the home directory.
3. Create a file within the mounted volume.
4. Delete it.

OBSERVED RESULT
1. ".Trash-1000" is created with the expected "files" and "info" folders, but the deleted file can't be found within them.
2. Checking "~/.local/share/Trash/" reveals that the deleted file has been moved there.

EXPECTED RESULT
1. The deleted file should be moved to the local ".Trash-1000" folder within the volume instead of "~/.local/share/Trash/"

SOFTWARE/OS VERSIONS
Dolphin: Version 25.08.1
Operating System: Kubuntu 25.10
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2
Kernel Version: 6.18.3-1-t2-questing (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-8210Y CPU @ 1.60GHz
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: Intel® UHD Graphics 617
Comment 1 FrostBird347 2026-01-06 07:34:23 UTC
*** Bug 514214 has been marked as a duplicate of this bug. ***
Comment 2 Oliver Schramm 2026-01-06 09:55:30 UTC

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