https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #5 from Peter Wibberley <p.wibber...@btinternet.com> --- All, Thank you for your comments. I presume that the value of 8192 for max_user_watches is the Neon default, as I haven't previously changed it (unless something else did). I had thought that, even if the value were very low and were causing baloo to fail, then doubling it should have made a difference. I've now tried 65472 (i.e. 65536 less a bit) (and confirmed the change with 'cat /proc/sys/fs/inotify/max_user_watches') but the problem still persists. Do you have any suggestions of how high a value of max_user_watches I should try? And are there any other diagnostics I can run? Many thanks and best regards Peter -- You are receiving this mail because: You are watching all bug changes.
