https://bugs.kde.org/show_bug.cgi?id=433204
Nate Graham <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REPORTED |CONFIRMED Ever confirmed|0 |1 CC| |[email protected], | |[email protected], | |[email protected] Keywords| |usability Product|frameworks-baloo |neon Assignee|[email protected] |[email protected] |e | Version|5.79.0 |unspecified Summary|Baloo File Indexing always |fs.inotify.max_user_watches |stops |is set to 8192, which is | |too low for Baloo to work | |properly Component|Baloo File Daemon |general --- Comment #2 from Nate Graham <[email protected]> --- Indeed it is, at least based on my wife's Neon system in its default configuration. That is indeed absurdly low. On my openSUSE Tumbleweed system, it's 65536. I wonder if this could be what's behind a lot of the "Baloo doesn't work!" complaints we get--at least for Neon users. Moving to Neon; hopefully this can be increased! -- You are receiving this mail because: You are watching all bug changes.
