In the last week or so (so i’m assuming after a system update) the Dolphin file manager has been reporting the error “Could not rename file [filename]” when I attempt to delete a file.
What is odd that while the first attempt to delete the file fails, if I try for a second time it then succeeds.
My guess is that this is a permissions issue on a temp or “trashcan” folder. Poking around I can see the ~/.local/share/Trash directory structure, but everything in there looks to be writable by my user ID, so i’m not sure where the error is coming from.
Hi, @incans - I’m no expert, but I wondered: do you get the error independent of whether the file is local (i.e. on internal ssd, in your local home folder) or external (network share), or on a usb?
I am getting this error when moving files between folders on different drives. I am not sure about folders on same drive/partition. No errors on second attempt. Don’t know any bug reports related to it.
In my case there are no network drives involved. However the majority of my day to day user files are physically on a second drive, and then bind-mounted into my home directory. Thus it could be the case that files are being copied across drives when the user file is copied into the trash folder (which is still on the boot drive).
Just a thought, this couldn’t be something as silly as Dolphin trying to “mv” (rename) a file into the trash folder, without realising these are on separate drives/filesystems and (I asume?) cannot be hard linked, but instead need a real copy of the file at block level?