Bug 169263

Summary:	Unwanted disk wakeups (KDE-Menu / Dolphin etc)
Product:	[Unmaintained] kdelibs	Reporter:	Oliver Sloss <cndedicated>
Component:	general	Assignee:	kdelibs bugs <kdelibs-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	finex
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Oliver Sloss 2008-08-16 21:31:33 UTC

Version:            (using Devel)
Installed from:    Compiled sources
OS:                Linux

When opening the KDE Menu, all hard disks wake up which has files listed on the recently used list. This may also affects applications links which are not on the root disk.

When navigating to /media with Dolphin, it wakes up every single disk listed in there (i think to calculate the number of sub folders).


There are several other disk wakeup issues (like saveto-dialog with firefox) which i can not fully recognize what causes it.

Comment 1 FiNeX 2008-08-17 01:21:21 UTC

What do you suggest?

Comment 2 Oliver Sloss 2008-08-17 07:32:26 UTC

It's absolutely not necessary to wake up the hard disks for the menu entries, this can be cached. (At the current state I have to wait until the hard disks are all spinned up, just to access the Menu. Because i have 16 disks it can take a very long time. also note: this also happens for remote files)

There should be either an option for Dolphin to disable subfolder content counting generally/specific or let a hidden file in the folder do this.


The other issues have to be tracked down and fixed one by one, i dont think there can anything tricky generally "protect" sleeping disks.

Comment 3 FiNeX 2008-08-17 11:00:29 UTC

Caching could be helpful... moreover I don't know in which layer this could be solved: directly on kdelibs or more higher at level application?

I change the product to kdelibs, maybe there are someone which can help on this.

Comment 4 Christoph Feck 2011-12-20 02:00:51 UTC


*** This bug has been marked as a duplicate of bug 166881 ***