https://bugs.kde.org/show_bug.cgi?id=516640

            Bug ID: 516640
           Summary: Trash is not found inside bind mounted directory
    Classification: Applications
           Product: dolphin
      Version First 25.12.1
       Reported In:
          Platform: Manjaro
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: ---

Created attachment 190043
  --> https://bugs.kde.org/attachment.cgi?id=190043&action=edit
Error message about no trash available

SUMMARY

I have a directory from another partition bind mounted into my home directory.
If I delete a file inside the mount point in my home directory, dolphin cannot
find the trash. If I delete a file inside the original directory there is no
problem.

STEPS TO REPRODUCE
1. Mount an ext4 partition e.g., a partition on an HDD at /media/intern/Dateien
via fstab entry
2. Bind mount a directory of this partition into your home directory e.g.,
which such a fstab entry:

/media/intern/Dateien/Downloads             /home/michael/Downloads      none  
bind        0       0


OBSERVED RESULT

If I open /home/michael/Downloads in dolphin and delete a file, I get a message
"The trash is not available for this item's location. Permanently delete it
instead?" and I only can delete the file permanently instead of moving it to
the trash.

If I open /media/intern/Dateien/Downloads in dolphin and delete a file, it gets
moved to the trash as expected.

EXPECTED RESULT

Independent of the path how I access the directory, the file get moved to the
trash.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro Linux 
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2

ADDITIONAL INFORMATION

The same behavior is also in version 25.12.2 of dolphin, which I installed
today. I have no problem with the same setup before version 25.12.1.

I cannot find any existing issue that describes the same problem, but 490247
and 516455 are maybe related to my problem to some degree.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to