Created attachment 142228 [details] Screencast If you rapidly press Delete then Enter twice in succession on a file, Krusader will first queue the file for deletion, then attempt to delete the deleted file. Maybe queuing a single file for deletion is overkill? Or maybe there should be a nicer lock mechanism in place?
I tried that test and couldn't reproduce the bug even using a computer from 2015, with a spinning HDD, and the git version of Krusader.
Can you follow the steps of https://commits.kde.org/krusader?path=INSTALL in order to build the git version of Krusader and tell us if your problem is solved?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!