Bug 464583 - Krunner search does not list files without extension
Summary: Krunner search does not list files without extension
Status: RESOLVED DUPLICATE of bug 457522
Alias: None
Product: krunner
Classification: Plasma
Component: filesearch (show other bugs)
Version: 5.26.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: baloo-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-21 08:31 UTC by yvan
Modified: 2023-01-29 20:28 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description yvan 2023-01-21 08:31:20 UTC
Hi,

I think I have read something about a similar issue a few months ago, maybe on planet.kde.org, but could not find it in Bugzilla: please apologize if this is a duplicate.

I have a lot of text files without extension, which are properly indexed by Baloo because 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). However, when I do a search from Kickoff or Krunner, it does not find those files without extension. Those are only found if I they have been opened recently.

Would it be possible to get search results for files without extension in Krunner and Kickoff?

Regards,
Yvan

Linux/KDE Plasma: Debian testing
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7
Comment 1 Natalie Clarius 2023-01-25 21:39:02 UTC
Can you please post the output of `balooshow -x path/to/the/file` for some of the files affected.
Comment 2 yvan 2023-01-27 15:42:43 UTC
(In reply to Natalie Clarius from comment #1)
> Can you please post the output of `balooshow -x path/to/the/file` for some
> of the files affected.

Of course:

```
$ LANG=C balooshow -x "/home/yvan/Nextcloud/some directory/Name First-Name"
The document IDs of the Baloo DB and the filesystem are different:
Url: /home/yvan/Nextcloud/some directory/Name First-Name
ID:       87531433492519 (DB) <-> 87531433492524 (FS)
Inode:    20380 (DB) == 20380 (FS)
DeviceID: 39 (DB) <-> 44 (FS)
4f9c0000002c 44 20380 /home/yvan/Nextcloud/some directory/Name First-Name
        Mtime: 1605520551 2020-11-16T10:55:51
        Ctime: 1659451494 2022-08-02T16:44:54

Internal Info
Terms: Mapplication Moctet Mstream 
File Name Terms: Fname Ffirst Fname 
XAttr Terms:
```
Comment 3 tagwerk19 2023-01-27 17:06:22 UTC
(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
Comment 4 Natalie Clarius 2023-01-27 18:09:06 UTC
Thanks. Yes, this is the same issue as https://bugs.kde.org/show_bug.cgi?id=457522.

*** This bug has been marked as a duplicate of bug 457522 ***
Comment 5 yvan 2023-01-29 20:28:11 UTC
Thanks tagwerk19 and Nathalie!