https://bugs.kde.org/show_bug.cgi?id=424680
--- Comment #2 from andre.fritz...@t-online.de --- Hi David, thanks for your answer. I'm not a specialist in computing, only a user with some experience. I hope, the screenshots are helpful. I had downloaded some exe-files. After this I started Krusader, marked this 17 files on the right source window (download folder) and then I used F5 (because of my bad experiences with F6) to copy to another folder in the left window of krusader (destination folder). I had the intention to delete files on the right sight after this - Krusader crashed during copying the third file. I did not change any rights. Then I started to copy single files. By copying the first and the second file - no problem. And they have been copied before - by the first action. The third single file causes the crash. Crash report did not work (I was acting as sudo!). So what can I do?? I like Krusader and use it from my beginning with OpenSuse 9.x After this: Double commander 1.0.0 alpha did the work. Dolphin did the work once again. MC did the work also (and I was not the sudo!). I'm sure, it is a task of krusader. I hope I could help. I wish you a lot of success. Thanks for your work. André -------- Weitergeleitete Nachricht -------- Betreff: [krusader] [Bug 424680] Krusader crashs after the command F6 (move files) Datum: Mon, 10 Aug 2020 09:03:10 +0000 Von: Davide Gianforte <bugzilla_nore...@kde.org> Antwort an: bug-cont...@kde.org An: andre.fritz...@t-online.de https://bugs.kde.org/show_bug.cgi?id=424680 Davide Gianforte <dav...@gengisdave.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dav...@gengisdave.org Resolution|--- |WAITINGFORINFO Status|REPORTED |NEEDSINFO --- Comment #1 from Davide Gianforte <dav...@gengisdave.org> --- Do you have a crash report? Is there a file with the same name in the destination folder? In that case, do you see the KIO window asking for an action? You said you can do the same operation in Dolphin (which means it shouldn't be a KIO bug), but without a trace it's hard to find the lines of code involved. -- You are receiving this mail because: You are watching all bug changes.
