20 Oct
2014
20 Oct
'14
9:48 p.m.
On Mon, Oct 20, 2014 at 04:17:55PM -0500, Timothy Pearson wrote:
I haven't experienced this which is why I
haven't commented. That being
said, you could try running kbuildsycoca --noincrememntal (as the user
experiencing the problem) to fully regenerate the database and see if that
helps.
Maybe I should have been more inclined to experiment... this option
did indeed restore the cache.
But after a week of restoration of data from a crashed hard disk,
during which each inconsiderate experiment can lead to more data,
I was probably overly cautious...
Thanks a lot! (Adding this to my collection of useful recipes.)
--
valgrind python -c 'for i in range(1,1): print(i)' 2>&1 | grep error