Yes, apparently this issue is known upstream, this makes baloo useless in i386,
and of limited use in amd64.
Also baloo upstream needs a new maintainer, my recommendation is to stop using
it. :-(
We should probably try to remove it from stretch.
On October 6, 2016 3:15:57 PM GMT+02:00,
Package: baloo-kf5
Version: 5.26.0-1
Followup-For: Bug #835562
Dear Maintainer,
just want to inform you, that the bug is still existent in the latest
version.
Thanks for reading this.
Best regards
Hans
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy:
Package: baloo-kf5
Version: 5.25.0-1
Followup-For: Bug #835562
I have the same problem.
I'm on a 64-bit system and the indexing stop at ~65000 files.
The number is not always the same, first time was 65535, after adding some
files and reindexing now is 68701.
/sbin/sysctl fs.inotify
Hi Maximiliano,
please take a look at the last strace output of baloo_file to see, which files
get opened by baloo:
strace -e trace=open baloo_file_extractor
open("/usr/lib/i386-linux-gnu/qt5/plugins/kf5/kfilemetadata/
kfilemetadata_taglibextractor.so", O_RDONLY|O_CLOEXEC) = 7
I do not know, if that matters, but maybe I should mention, that my ~/home is
on an encrypted filesystem (dm-crypt, luks).
It is a SSD, and the filesystem is formatted with ext4.
However, the same construct is made on my 64-bit system, where baloo is
working like a charm (also SSD drive, and
Hi Maximiliano,
> What's the output of "/sbin/sysctl fs.inotify" in your failling machine?
this is the output:
/sbin/sysctl fs.inotify
fs.inotify.max_queued_events = 16384
fs.inotify.max_user_instances = 128
fs.inotify.max_user_watches = 65536
>
> Can you check the debug output of the file
Control: tag -1 + moreinfo
¡Hola Hans!
El 2016-08-27 a las 09:36 +0200, Hans escribió:
meanwhile I tried the package from unstable, but got the same result: stopping
after an amount of directories.
Meanwhile I could proove, that the bug is not caused by empty directories.
FYI: balooctl
Dear maintainers,
meanwhile I tried the package from unstable, but got the same result: stopping
after an amount of directories.
Meanwhile I could proove, that the bug is not caused by empty directories.
FYI: balooctl status shows:
balooctl status
Baloo File Indexer is running
Indexer
Dear maintainers,
now I can tell more: baloo_file stops at exactly 5499 opened files. With opened
files I do not mean indexed files, but files, baloo_file has opened during its
run. It can be proven by running the strace command, I mentioned in my first
bugreport. Looks like baloo_file is
Package: baloo-kf5
Version: 5.23.0-1
Severity: important
Dear Maintainer,
I found out, that baloo is not working well, as it should.
There are two weired behaviours, which might be caused by the same reason.
1. Most important: baloo is stopping indexing at around 5000 indexed files. I
guess,
10 matches
Mail list logo
