Re: [arch-general] KDE update and baloo

2014-04-19 Thread Mike Cloaked
On Thu, Apr 17, 2014 at 8:33 PM, Genes Lists wrote: > On 04/17/2014 10:37 AM, Lukas Jirkovsky wrote: > >> >> 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. >> >> No not using PIM. I killed off all the balo

Re: [arch-general] KDE update and baloo

2014-04-17 Thread André Vitor
On Thu, Apr 17, 2014 at 4:33 PM, Genes Lists wrote: > On 04/17/2014 10:37 AM, Lukas Jirkovsky wrote: > >> >> 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. >> >> No not using PIM. I killed off all the balo

Re: [arch-general] KDE update and baloo

2014-04-17 Thread Genes Lists
On 04/17/2014 10:37 AM, Lukas Jirkovsky wrote: 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. No not using PIM. I killed off all the baloo processes - short term fix.There really should be an off button on

Re: [arch-general] KDE update and baloo

2014-04-17 Thread Lukas Jirkovsky
On Thu, Apr 17, 2014 at 3:11 PM, Genes Lists 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

Re: [arch-general] KDE update and baloo

2014-04-17 Thread Evgeniy Alekseev
On Thursday 17 April 2014 09:11:35 Genes Lists 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 runni

[arch-general] KDE update and baloo

2014-04-17 Thread Genes Lists
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 c