[dolphin] [Bug 444652] New: Dolphin allows the user to move to the trash files that cannot actually be removed by him

Luca Carlon bugzilla_noreply at kde.org
Sat Oct 30 10:07:01 BST 2021


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

            Bug ID: 444652
           Summary: Dolphin allows the user to move to the trash files
                    that cannot actually be removed by him
           Product: dolphin
           Version: 21.08.2
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: dolphin-bugs-null at kde.org
          Reporter: carlon.luca at gmail.com
                CC: kfm-devel at kde.org
  Target Milestone: ---

SUMMARY
In some cases dolphin allows to move to the trash bin directories that cannot
be actually removed by the current user.

STEPS TO REPRODUCE
1. Create a directory owned by the current user: mkdir somedir
2. Create a directory owned by root inside somedir: sudo mkdir rootdir
3. Create a file owned by root inside rootdir: sudo touch file
4. Move to the trash bin the entire directory "somedir".

OBSERVED RESULT
Dolphin allows the user to remove the directory, and places it in the trash
bin. Once the user tries to empty the trash bin, an error is returned. This may
be pretty bothering cause a user won't be able to empty the trash until he
finds what must be moved out of the bin.

EXPECTED RESULT
IMO the user should not be allowed to send "somedir" to the trash bin, although
"moving" is technically possible. Sending to the trash bin should be possible
only when "removing" is actually allowed.
The result is that a user won't be able to empty the trash bin anymore without
fixing the problem manually, by restoring what is blocking the procedure. This
does not seem very user-friendly.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.14.10-1
(available in About System)
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the kfm-devel mailing list