Summary: | deleting a file the whole folder got deleted (and no way to restore) | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | Duns <web> |
Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | REPORTED --- | ||
Severity: | critical | CC: | kde.aerospace405, kfm-devel, rm, sts33nvyb, web |
Priority: | NOR | ||
Version: | 21.08.2 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Duns
2021-10-23 07:13:44 UTC
It happened one time, so far. Other attempts show a normal behavior of Dolphin. However a deleting misbehavior happen always on the Desktop, as I said: impossible delete anything. So I guess that there is something wrong in KDE delete graphical command. Maybe it could be relevant say that that folder was an amule one: deleting a file in Incoming subfolder, the whole root folder (Amule) was deleted. Today I deleted a file from Amule/Incoming folder and nothing wrong happened. So far I didn't any other cases of this bug. I had this happen to me today too, with Dolphin 20.04.2, opensuse 15.2. Here's what happened: 1. I decided I needed to free up some disk space, as I only had about 12 GB free on my home partition. I decided to delete old mod files from the directory ~/download/games/skyrim, which is where I download mods for skyrim. The directory had about 200 files in it, some of them over 1 GB in size. 2. I opened Dolphin and navigated to ~/download/games/skyrim. 3. I went through the directory contents, selecting old mod files that I wanted to delete by clicking on the "+" symbol in the upper-left corner of each file icon. 4. I clicked on the "File" menu and then the "Delete" menu item. 5. A window appeared asking if I was sure I wanted to delete 73 files. I confirmed. 6. I closed Dolphin. 7. A few hours later, I discovered that the directory ~/download/games/skyrim no longer exists. All the files are gone. All subdirectories are gone. Looks like this is very similar to my situation. Please check out #491027 I also have steps to reproduce there. https://bugs.kde.org/show_bug.cgi?id=491027 Oops, I'm sorry. I didn't read it properly. No, my bug isn't quite the same, but it is similar. |