https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #23 from tagwer...@innerjoin.org ---
You're the first one that's happened to :-)
So, I blindly followed the "How to create useful crash reports" and was able to
run
coredumpctl
and get a list of crash dumps, with their "process
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #22 from Peter Wibberley ---
(In reply to tagwerk19 from comment #21)
> I think we do need someone who knows to come in here...
>
> A couple of observations might help though, I see lines like:
>
> ioctl(14, FIONREAD, [32])
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #21 from tagwer...@innerjoin.org ---
I think we do need someone who knows to come in here...
A couple of observations might help though, I see lines like:
ioctl(14, FIONREAD, [32]) = 0
read(14,
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #20 from Peter Wibberley ---
(In reply to tagwerk19 from comment #19)
> I would look though at what baloo_file had started to index when it started
> to log errors, maybe it's possible to see something strange...
>
> You can exclude
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #19 from tagwer...@innerjoin.org ---
I would look though at what baloo_file had started to index when it started to
log errors, maybe it's possible to see something strange...
You can exclude folders from indexing, either through system
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #18 from Peter Wibberley ---
(In reply to tagwerk19 from comment #17)
Tagwerk19,
Thank you for the suggestion.
No need to kill the process, as it's dying anyway.
You're not wrong about shedloads: over 20MB and 200,000 lines
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #17 from tagwer...@innerjoin.org ---
I think that baloo_file watches directories (mostly) and not files.
I get this info from a trick of killing the baloo_file process and starting
from the command line under strace. So...
ps ax | grep
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #16 from Peter Wibberley ---
(In reply to Harald Sitter from comment #15)
> I can't really say anything about that I know nothing about baloo. The
> inotify cap needs fixing one way or another, but if increasing the cap
> doesn't help you I
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #15 from Harald Sitter ---
I can't really say anything about that I know nothing about baloo. The inotify
cap needs fixing one way or another, but if increasing the cap doesn't help you
I guess your problem has nothing to do with it.
--
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #14 from Peter Wibberley ---
(In reply to Harald Sitter from comment #13)
The thing I don't understand is that, up until 17 December, I would have had
max_user_watches set at 8192 with the number of files not being significantly
less than
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #13 from Harald Sitter ---
(In reply to Jonathan Riddell from comment #10)
> I wonder if this should be built into baloo rather than being distro specific
It will sort itself with kernel 5.11. Well, to a degree.
If my maths is correct
https://bugs.kde.org/show_bug.cgi?id=433204
Peter Wibberley changed:
What|Removed |Added
Summary|fs.inotify.max_user_watches |Baloo File Indexer will not
12 matches
Mail list logo
