Bug 517795 - Moving to Trash on Samba Mounted Shares no longer works
Summary: Moving to Trash on Samba Mounted Shares no longer works
Status: RESOLVED DUPLICATE of bug 518012
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: Trash (other bugs)
Version First Reported In: 6.24.0
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-03-18 20:36 UTC by Ben Erickson
Modified: 2026-06-04 11:40 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Erickson 2026-03-18 20:36:53 UTC
SUMMARY
Prior to 6.24.0, when a samba share was mounted and a file was deletedo on the share, a Trash folder was created on the root of said share and deleted files were successfully moved into it.

After upgrading from kf6-kioworker 6.23.0 to 6.24.0, kioworker no longer successfully creates a Trash folder on the root of the share and throws the following error:

```
Mar 18 13:17:59 workstation kioworker[16621]: Creating trash for "/" failed - no permission?
```

It may be attempting to create the Trash folder on the root of client instead and failing to do so for permissions issues.  As a result, files that are removed are done so permanently.  When deleting a file on the share in Dolphin, for instance, a prompt appears stating: "The trash is not available for this item’s location. Permanently delete it instead?"

STEPS TO REPRODUCE
1. Create a samba mount with the following configuration settings in smb.conf:
```
[share_name]
path = /path/to/share_name
browseable = yes
writeable = yes
valid users = user
create mask = 0644
directory mask = 0755
guest ok = no
follow symlinks = yes
wide links = yes
```
2. Create a systemd mount and automount file.
Systemd Mount File:
```
[Unit]
After=network-online.target
Description=Mount fileserverfqdn share_name
OnFailure=automount-restarter@%N.service

[Mount]
What=//fileserverfqdn/share_name
Where=/mnt/share_name
Type=cifs
Options=auto,nobrl,rw,x-systemd.device-timeout=5,file_mode=0644,dir_mode=0755,vers=3.11,uid=<uid_of_user_mounting>,gid=<gid_of_group_mounting>,nofail,credentials=/etc/fstab.d/creds.conf,_netdev,context="system_u:object_r:cifs_t:s0"
DirectoryMode=0755

[Install]
WantedBy=multi-user.target
```
Systemd Automount File:
```
[Unit]
Description=Mount fileserverfqdn share_name share

[Automount]
Where=/mnt/share_name

[Install]
WantedBy=multi-user.target
```
3. Run `systemctl daemon-reload`
4. Open Dolphin and navigate to the `/mnt` directory which should then automatically mount the samba mount.
5. Create a file or folder on the share and then delete it. 

OBSERVED RESULT

Trash folder is not created in /mnt/share_name/.Trash-${uid} or it is not used if it is created manually.  File is removed permanently instead.

EXPECTED RESULT

Trash folder is created in /mnt/share_name/.Trash-%{uid} and files deleted on the share in Dolphin are moved there.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Operating System: Fedora Linux 43
KDE Plasma Version: 6.6.2
KDE Frameworks Version: 6.24.0
Qt Version: 6.10.2
Kernel Version: 6.19.8-200.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
Memory: 32 GiB of RAM (31.2 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 2070

ADDITIONAL INFORMATION

Related bugs: https://bugs.kde.org/show_bug.cgi?id=490247
Related commits (maybe?): https://invent.kde.org/frameworks/kio/-/commit/5e98d7d0fe8a2b0c80ed450193ffcbd2c95378d6
Comment 1 Ben Erickson 2026-03-18 20:44:33 UTC
The user who created the related bug https://bugs.kde.org/show_bug.cgi?id=490247 appears to be reporting a separate issue: the individual wants files deleted in fuse-mounted directories to be moved to the Trash within those fuse-mounts and not into their ~/.Trash folder.  The issue reported in this bug pertains to files explicitly deleted in a remote share that NEVER moved deleted files into ~/.Trash and instead moved deleted files into the mounted share's Trash as intended.  For instance /mnt/share_name/.Trash.  Hence, I don't think this is a duplicate.
Comment 2 Pedro V 2026-05-04 03:32:05 UTC
It's not just Samba, my setup using NFS is affected, and generally seems to be an issue affecting mounts in general, not requiring networking.
The report is further complicated by Trash directory auto-creation which already have issues in the past.

If networking is indeed unrelated, then bug 518012 might be a duplicate.
Do note that a Samba mount is also being discussed there, so there's definitely duplication of information.

On my NFS share looking quite like rootfs with per-user homes, I have a per-home Trash (wasn't used earlier), and a per-user Trash in the mount root (was the one used earlier), but after an update, trashing just fails silently in GUI, showing `kf.kio.workers.trash: Creating trash for "/" failed - no permission?` in terminal.

KDE Plasma Version: 6.6.4
KDE Frameworks Version: 6.24.0
Comment 3 Oliver Schramm 2026-06-04 11:40:27 UTC

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