https://bugs.kde.org/show_bug.cgi?id=340485
Stefan <pralltgaranti...@flusskilometer.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pralltgarantiert@flusskilom | |eter.de --- Comment #3 from Stefan <pralltgaranti...@flusskilometer.de> --- I can reproduce, especially comment 1: Kleopatra Version 2.2.0-gitfb4ae3d (2015-11-12) Unter KDE 4.13.3 on Windows 10 64bit (Pro), should be up to date as of 2017-01-17 Intel Core i5-4670K @ 3.4 GHz sha256sum.txtHp2692.new sha1sum.txtHp8528.new are generated for a 3.91 GB large file (4102945 KB), moving file to sha256sum.txt failed: Error renaming the file. Unfortunately the executables seem single threaded. Running "sha256sum.exe filename.iso" directly in the windows commandline gives me a checksum after 42 seconds. So it is difficult to look for a timeout. One core of my system is on 100% load. Moving the large file to an SSD does not speed this up. So I can't easily test if it is a time out or a file size problem. >From a 1.67 GB (1758561 KB) large file the checksums are correctly calculated and saved. >From HDD: sha256sum.exe has a run time of ~19 seconds >From a USB thumbdrive on USB3: 19 seconds Same drive on USB 2: 44 s Kleopatra on USB 2: could not move file after 32 seconds But Window's USB-File-Caching let's me successfully finish a second run on the same file in under 30 seconds. (To avoid the use of cached thumbdrive data, I did my test always on a freshly plugged in drive and verified the read speed in the Windows Resource Monitor.) -- You are receiving this mail because: You are watching all bug changes.