On Fri, May 2, 2014 at 11:13 AM, Luca Beltrame
In data venerdì 2 maggio 2014 11:01:24, C ha scritto:
So why would Baloo be churning for so many hours... and is there a way to see what Baloo might be stuck on?
Use pgrep or equivalent to look up the full command line list of baloo_file_extractor: it'll be a list of numbers.
Use "balooshow <number>" to gain insights on the type of file. Being extracted. Usually some file types, in particular text (if large, > 20M) can stress the extractor a bit (a more efficient solution is being investigated as we speak - it's under review).
I don't know pgrep so well... not sure if I'm using it right pgrep -l baloo 1333 baloo_file 18540 baloo_file_extr That didn't look right so I tried this: pgrep -a baloo 1333 /usr/bin/baloo_file 18540 /usr/bin/baloo_file_extractor 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 223 222 221 220 219 That looks more like what you were referring to... but balooshow gives me this: balooshow 239 QSqlQuery::prepare: database not open Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) No index information found It's the same for all numbers in that list. I think I'm having a PEBKAC moment. :-P C. -- openSUSE 13.1 x86_64, KDE 4.13 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org