https://bugs.kde.org/show_bug.cgi?id=480111
Bug ID: 480111 Summary: Deleting a symlink is impossible if the disk of the target is close to full Classification: Applications Product: dolphin Version: 23.08.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sasori.n...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I have 2 HDDs, drive A and drive B. Drive A is close to full (only 50GB left). Drive A also contains a 60GB file (file_1). I create a symlink to this file on drive B. I select the symlink, hit "delete" and I see a message "There is not enough space on the disk to write file:///mnt/driveB/file_1". The only way I can delete the symlink is to drop to a console (or unplug drive A, that seems to work too, since this makes the symlink invalid -> 0B). Short of that available space problem, the symlink gets deleted normally, on the same drive's trash as the symlink (no cross-filesystem move), so that part works fine. It's only the pre-delete check that seem to make weird assumptions. STEPS TO REPRODUCE 1. Have two drives, one close to full (drive A), the other not (drive B) 2. Find a file on drive A with a size greater than the remaining space available on A (create it if necessary). 3. Create a symlink to that file on drive B. 4. Select the symlink, hit delete. OBSERVED RESULT A message "There is not enough space on the disk to write file:///path/to/driveB/big_file" appears. EXPECTED RESULT The symlink should be in drive B's trash. SOFTWARE/OS VERSIONS Linux: Linux kernel 6.1.71-1-MANJARO (64-bit) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 -- You are receiving this mail because: You are watching all bug changes.