https://bugs.kde.org/show_bug.cgi?id=480665
--- Comment #5 from tagwer...@innerjoin.org --- (In reply to Martin Tlustos from comment #3) > As I said, copying with cp was a lot faster. I guess, dolphin and baloo have > some kind of connection that slows dolphin down in copying even when the > folder is an indexed one. (In reply to Martin Tlustos from comment #0) > Went back to Linux, tried to copy from command line (cp): about as fast as > windows. > Then I disabled baloo, and it copied the same file again in about 20 seconds. Looks like I missed that you were copying in Dolphin (with just the one test with cp). No problem, I will look to see if I see anything. (In reply to Martin Tlustos from comment #4) > Maybe dolphin puts some temporary files somewhere in my home folders that > baloo wants to index because the specific folder is not excluded? As far as I know, no. Maybe I remember that in the case of Baloo, that does not make use of workfiles even when doing content indexing. Can you check "systemctl status --user kde-baloo" when you've got Baloo running and the copy is slow? That's to see whether Baloo is working within its 512 MB memory cap. What do you get with a "kmimetypefinder" for the file, it is properly recognised? -- You are receiving this mail because: You are watching all bug changes.
