https://bugs.kde.org/show_bug.cgi?id=464583
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagwer...@innerjoin.org
--- Comment #3 from tagwer...@innerjoin.org ---
(In reply to yvan from comment #0)
> ... I can find them with `baloosearch somename` (each file, with
> or without extension, is even returned four times, I don't know if this is
> normal or not) ...
You can try:
$ baloosearch -i somename
This will show the "hits" together with the DocId that baloo has for the file
(the DocId being a concatenation of the device and inode number).
You don't say what filesystem you are using but I'm guessing you'll find
baloosearch gives your "hits" with different device numbers. Your "balooshow"
results gives a hint.
(In reply to yvan from comment #2)
> Inode: 20380 (DB) == 20380 (FS)
> DeviceID: 39 (DB) <-> 44 (FS)
Could be that you are using BTRFS (or possibly a "remote" fuse mount?) BTRFS
has the "problem" that you might get different device numbers each time you
reboot - and baloo then thinks it's got a completely new set of files to index.
Have a look at:
https://bugs.kde.org/show_bug.cgi?id=402154#c12
For the "not being shown by krunner" part of the question:
(In reply to yvan from comment #2)
> ...
> Terms: Mapplication Moctet Mstream
> File Name Terms: Fname Ffirst Fname
Balooshow "says" that baloo thinks the file is an application/octet-stream, not
a text file. It would be worth looking at Bug 457522
--
You are receiving this mail because:
You are watching all bug changes.
