Results 1 to 3 of 3

Thread: Dolphin file manager unpleancy

  1. #1
    Join Date
    Mar 2011
    University of Cologne

    Default Dolphin file manager unpleancy

    Sometimes the Dolphin file manager displays a "waiting bar" with a blue dot moving left and right all the time. It makes me nervous!

    There is a message next to it, stating that the file folder is being loaded. But I do not know that there is anything happening, nor is there any need to load anything. There is also a little red "delete" button, but klicking on it achieves nothing.

    How can I get rid of this nuisance?

  2. #2
    Join Date
    Jun 2008
    Earth - Denmark

    Default Re: Dolphin file manager unpleancy

    what operating system and version are you using?
    i suppose you are using KDE, but which version?

    you say sometimes this happens--does it always happen in certain
    directories, but never in some certain others?

    are these directories on your local machine? in an internal hard
    drive, or on an USB attached drive? or, maybe it is on another machine
    on the local area network or maybe on the other side of earth? do
    you always see this 'nuisance' on distant drives, but not local
    drives? etc

    and, please the next time you see this dot moving please take a screen
    shot and up load it to, give us the url..

    this delete button, what would you suppose it would delete?

    [NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.1.8, nVidia
    173.14.28 3D, Athlon 64 3000+]
    "It is far easier to read, understand and follow the instructions than
    to undo the problems caused by not." DD 23 Jan 11

  3. #3
    Join Date
    Jun 2008
    San Diego, Ca, USA
    Blog Entries

    Default Re: Dolphin file manager unpleancy

    I usually see that reading externally connected storage (eg USB) which has "gone to sleep" and needs to be woken up.
    Recently have experienced that reading internal drives even when on the same drive as the system partition if haven't accessed for a very long time.

    In the former case, the cause is clear. The drive has to be actively spinning to be read.
    in the latter case, my guess is that resources need to be re-allocated but since it's only a recent development I've noticed I haven't studied it for very long.

    So, it can make a diff what is the folder you're accessing. Besides "normal" directories, *NIX file systems typically use the folder metaphor representing block devices (eg drives) as well and the situation is different.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts