https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #12 from tagwer...@innerjoin.org ---
I tried creating a:
/etc/sysctl.d/40-neon-inotify.conf
file, added the line
fs.inotify.max_user_watches=129762
and rebooted. Checked with:
sysctl fs.inotify.max_user_watches
and got:
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #11 from Peter Wibberley ---
Jonathan,
Tried 129762, but I still have the problem.
Incidentally, I tried running 'balooctl monitor' and then 'balooctl enable'
from another Konsole. I got the messages as follows:
Waiting for file ind
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #10 from Jonathan Riddell ---
I compiled configure-inotify and made systemd start the service and I got a new
file made
> cat /run/sysctl.d/40-neon-inotify.conf
# This file gets auto-generated by neon-configure-inotify. Changes will be
over
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #9 from Peter Wibberley ---
I have no idea whether this is significant. As per my original message,
Dolphin stopped displaying any timeline on 17 December 2020 (which is how I
noticed baloo wasn't working). From an inspection of var/log/ap
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #8 from Nate Graham ---
(In reply to Harald Sitter from comment #4)
> Wasn't there a GUI that tells the user about inotify exhaustion?
Hmm, not to my knowledge.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #7 from Harald Sitter ---
FTR 8192 was the default value of the kernel up to 5.11 where it was changed to
the dynamic calculation known from epoll
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/notify/inotify/in
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #6 from tagwer...@innerjoin.org ---
I think the questions to ask are...
How many folders do I have?
After I increased the value, do I still get the
"... File changes will be ignored." messages?
Am I running anything else
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #5 from Peter Wibberley ---
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
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #4 from Harald Sitter ---
Wasn't there a GUI that tells the user about inotify exhaustion? I distinctly
recall Vishesh talking about it at some meeting or other. Though I realize that
may have been just musings and what I recall in the back
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #3 from tagwer...@innerjoin.org ---
> ... File changes will be ignored
When the limit is reached iNotify stops flagging _any_ changes (for that user),
not just that adding a new watch fails?
Tweaking the limit gradually down until I start se
https://bugs.kde.org/show_bug.cgi?id=433204
Nate Graham changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
11 matches
Mail list logo
