[dolphin] [Bug 482902] New: Data loss on remote mount when using rmdir in terminal

Evan 'JabberWokky' Edwards bugzilla_noreply at kde.org
Fri Mar 8 18:04:04 GMT 2024


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

            Bug ID: 482902
           Summary: Data loss on remote mount when using rmdir in terminal
    Classification: Applications
           Product: dolphin
           Version: 23.08.1
          Platform: Kubuntu
                OS: Linux
            Status: REPORTED
          Severity: major
          Priority: NOR
         Component: panels: terminal
          Assignee: dolphin-bugs-null at kde.org
          Reporter: evan+kdebugs at cheshirehall.net
                CC: kfm-devel at kde.org
  Target Milestone: ---

I just lost a fair amount of data (luckily non-critical) because dolphin in 5.x
(I checked three recent versions) behaves in the following manner:

1. If a remote directory is not explored, it appears empty within the
filesystem (displaying 0 items in the panel)
2. If you then use `rmdir *` in the terminal to clear empty directories,
leaving those that have files, the remote mounted filesystem has the same
structure, so rmdir dutifully removes all directories including all files.

**Reproduction:**

This can be reproduced via this on the remote system (via ssh or some other
"hidden from dolphin" method):

`mkdir -p $HOME/test/foo/bar ; echo MyData >$HOME/test/foo/bar/file.txt`

Then go to $HOME/test using sftp: url in dolphin, open the terminal and type
`rmdir foo`

**Observed behavior:**

All data and files are removed from the mounted filesystem.

**Expected behavior:**

rmdir should see files inside the directory and not remove the directory.

---
I have not tested under KDE 6, but did test under a couple other 5.x Plasma
desktops and observed the same behavior. 

[Administrivia note: I searched for this bug and the appropriate
classification; I assume dolphin may be incorrect, but couldn't determine the
correct classification.  Please reclassify to the correct software!]

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


More information about the kfm-devel mailing list