Version: (using KDE 4.4.0) OS: Linux Installed from: Ubuntu Packages I`m on Kubuntu Karmic 64bit, using KDE SC 4.4 from the kubuntu ppa-backports repository. When I have many files into a folder (many files for this bug I report, could be as many as 100 to 1000 or more) and I want to move them in another directory, the "cut" operation takes ages. Quite slow, but not as much as the "cut", are the "paste" and "move to" operations. On a test performed to cut 967 photographs in a folder, took 64 seconds! Of course the more the files, the slower the operation. For 224 files it took me 14 seconds. Dolphin or Konqueror becomes totally unresponsible at the time of the cut and my single core cpu usage goes on top, all consumed by dolphin.
Thanks for the report, but I could not reproduce the issue. I went into a folder containing 3000 html files and the cut operation took < 0.5 seconds. The start of the copy operation after doing a paste was also done immediately. Two root causes come to my mind: 1. Do your image files all have valid file extensions in their name? E. g. .jpg, .png, .gif... 2. All icons get greyed out. If there is an issue in the graphics driver, this can take ages... Did you enable compositing in your environment? Does it help if you start dolphin from the konsole with "dolphin -graphicssystem raster"?
1) Yes, all of my files have valid extensions but even without extensions at all the problems exists. I created 1000 dummy files with a bash while loop named from 0-999 (a=0; while [ $a -lt 1000 ]; do touch $a; a=`expr $a + 1`; done) Then it took several seconds to cut them. 2) No issue with my graphics card as I can tell, as compositing is working smoothly. I have a Nvidia 6600 GT graphics card. No luck using the "dolphin -graphicssystem raster". I have created a screencast demonstrating the problem and uploaded it on youtube. Please watch this video and guide me if I can somehow give you more information that might help. http://www.youtube.com/watch?v=nFbcByt2Z_I&fmt=22 (Youtube might not be able to show the video in HD yet as I have just uploaded it, so you can use the following alternative link to download it) http://nemesis.ee.teiath.gr/~ee4654/bug_227538.ogv
Thanks for the cool screencast. But I've still the problem that I cannot reproduce the issue. I've a similar configuration as you, but doing a a=0; while [ $a -lt 1000 ]; do touch $a; a=`expr $a + 1`; done followed by a 'cut' results in no measurable delay in my environment. Increasing the number to 10000 results in a blocking of a few seconds, but as the files have no file extension this is the "worst case scenario" (-> each file must be opened to guess the mime type), so this cannot be made a lot faster. In KDE SC < 4.4 we had such blocking issues in combination with enabled Nepomuk/Strigi. Those should not occur anymore, but could you please still try to temporary turn off Nepomuk and Strigi?
Without Nepomuk and strigi enabled, is faster but still slow... It needs at least 15 seconds for 1000 files. Sad that I can`t help :( If there is something else I can do (like installing the debug symbols and do whatever to "see" what dolphin is doing when it is using all this cpu power), please let me know.
I'd suggest to wait for KDE SC 4.4.1 before investigating further. There have been done some important file-related fixes after KDE SC 4.4.0 has been tagged and maybe (...) this corresponds with your issue. But I'm not sure. However if you want to check the root cause: - open the konsole and do a "valgrind --tool=callgrind dolphin --nofork" (-> dolphin gets profiled and will be very slow, just test it maybe with 100 files instead of 1000) - As output a huge profile file will be generated, after you closed Dolphin. This can be opened with kcachegrind to check the bottleneck. If the file is below 20 MB, you can just send it to me per e-mail. But please don't investigate too much time, just do it if you really like it to do :-)
Vangelis, I did not get similar reports yet. Would it be possible that you verify again whether the issue still occurs with KDE SC 4.5.0 (will be out very soon)? If this is the case, please reopen the bug again. Thanks!
Now I bought a new Laptop and formatted the old PC :) So I can't reproduce the bug... If I manage to see something similar I will re-open it. Thank you Peter!