On Thu, Apr 17, 2014 at 3:11 PM, Genes Lists <lists@xxxxxxxxxxxx> wrote: > After the update to 4.13 - i have baloo sucking up cpu cylces. I did go to > the desktop search and add every single file system/directory to the 'dont > scan' list. So there should be nothing left to scan. > > Didn't help - it's still running 2 hours later ... anyone know how to stop > this selfish cpu hog? > > > > thanks! Is it with KDE PIM? I remember a discussion in the release ML that baloo was somewhat broken in PIM. I dunno if that was fixed or not.
