Version: (using KDE 4.0.83) Installed from: Ubuntu Packages In KDE 4.1 beta 2 Dolphin locks up (I did not check CPU usage) and is unusable for up to 1 minute when performing actions (delete, move) on large numbers (>100) files. To test: 1) Download the latest Poppler release (http://poppler.freedesktop.org/) 2) Decompress to a directory. 3) Select all files, right click one, and select Delete. 4) ??? 5) Profit... no, wait!
This issue might be related to bug 164296 or bug 163050 (they have not been solved in 4.0.83). To be sure: Does the issue only occur if the information panel is open (I currently have no access to Dolphin and cannot test it myself)? Thanks!
Thanks. Disabling the Information panel prevents the slowdown. The issue only occurs if the Information panel is shown. I am not marking as dupe as there were no multimedia files present in my case, as is the case with bug 164296 and bug 163050. Feel free to mark as dupe if you see fit, however. Thanks.
Thanks for the update. I'll have to check myself first what might be the root cause, I think it's related to strigi but I'm not 100 % sure....
I have discovered that Dolphin can be made to be irresponsive even with the Information panel closed if there are enough files. Uncompress the current Digikam beta (http://sourceforge.net/project/showfiles.php?group_id=42641) and then select all the files. Try to delete them. Dolphin hangs, even with no Information panel.
I downloaded strigi and selected all files and Dolphin does not hang (no matter whether the Information Panel is shown or not). Could you please tell me in more detail what you mean with "hangs": - How did you select all files? With Ctrl+A? Does it already it already block here? - How did you delete the files? By openening the context menu (-> does it hang her in the meaning of that the context menu does not popup?) - Or did you use Shift+Del for deleting? Does the progress dialog for deleting open delayed? In my case deleting the files took less than halve a second...
I've already rm'ed the partition with 4.1b2 as I intend to triage rc1 next week. I'll check if I can reproduce the bug there and I'll report back. It will be in a few days time, though (exams).
The issue should be fixed now on trunk. Please reopen the bug if it still does not work in your environment. Thanks!