Version: unspecified (using KDE 4.6.1) OS: Linux After some unknown amount of time passed, the instance of dolphin displaying the home folder displayed a "Loading folder..." indicator at the bottom of the window, which never disappeared and is still running at time of filing this report. Reproducible: Couldn't Reproduce Steps to Reproduce: Out of the ~20 bugs I've filed in the past couple of days, this is the only bug I've never been able to reproduce. Actual Results: It never goes away! See screenshot to observe the loading bar in question. Expected Results: The loading bar should disappear if the folder has reloaded, or give up after a minute. Filed downstream at Kubuntu, includes many attachments and debugging information.
Created attachment 58007 [details] "Loading folder..." indicator on folder.
Thanks for the bug report! > Filed downstream at Kubuntu, includes many attachments and debugging > information. Can you provide the link to the downstream report?
Have the same issue in opensuse 11.4 (kde 4.6) This is really annoying.
https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/735252 - report in launchpad
@Peter What could Dolphin be waiting for here? Nepomuk? (as a guess) Reporters: is Nepomuk enabled/working on your systems?
In my case nepomuk is enabled and even listed in proc list :-D
@Will: The indicator is unrelated to Nepomuk. It will be started when a directory starts to load and KDirLister will emit a signal when it's finished. In 4.6.1 an issue has been introduced in KDirLister that might be the root-cause of this. This has been fixed a few days later and AFAIK distributions like Suse took care to patch 4.6.1. Everything should be fine in 4.6.2 again.
Can somebody still confirm this?
Yes, I can confirm this. I'm not sure how to trigger the bug, but I've noticed it happens when I have multiple tabs open and a file shown in one of the tabs gets modified (by a text editor, for example). The problem doesn't seem to happen when there's only one tab open. I'm using Dolphin 1.7 under KDE 4.7.4 in Debian Testing.
This problem is fixed in 4.8.3 - please reopen the bug-report if there might be still some situation where this problem occurs.