https://bugs.kde.org/show_bug.cgi?id=514150
--- Comment #3 from Richard Day <[email protected]> --- (In reply to Stefan Brüns from comment #2) > It does quit. It may just take a while until it has processed the current > work item. > > The BR is missing any details which would be needed to address any actual > problems. So you wouldn't consider baloo continuing to consume considerable CPU for at least 10 minutes after being disabled a problem? As a laptop user I would definitely consider this a problem, if I requested an application to quit and it took 10 minutes to do so I would consider that a bug, even if it didn't consume considerable CPU. Would you not? This behaviour makes it hard to leave baloo enabled on a laptop because it just drains the battery unnecessarily when the power is removed. -- You are receiving this mail because: You are watching all bug changes.
