Bug 439870 - Use files index does not work for disks in /media
Summary: Use files index does not work for disks in /media
Status: RESOLVED NOT A BUG
Alias: None
Product: kfind
Classification: Applications
Component: general (show other bugs)
Version: 21.04.3
Platform: Neon Linux
: NOR major
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-07-15 07:30 UTC by sg7e0f7m
Modified: 2021-07-15 14:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sg7e0f7m 2021-07-15 07:30:15 UTC
SUMMARY
When enabling use files index and I selected my other HDD no results are shown.

STEPS TO REPRODUCE
1. Configure baloo to index disk in /media
2. Open Kfind and select the disk indexed in step 1.
3. Check "Use files index" box.
4. Click on "Find" button.

OBSERVED RESULT
No results are presented.

EXPECTED RESULT
Results should be instantly presented.

Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-59-generic (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
Having "Use files index" box unchecked does present results for disk in /media.
Having "Use files index" box checked does present results for user's home directory.


/home/francois/.config/baloofilerc:

[General]
dbVersion=2
exclude filters=*~,*.part,*.o,*.la,*.lo,*.loT,*.moc,moc_*.cpp,qrc_*.cpp,ui_*.h,cmake_install.cmake,CMakeCache.txt,CTestTestfile.cmake,libtool,config.status,confdefs.h,autom4te,conftest,confstat,Makefile.am,*.gcode,.ninja_deps,.ninja_log,build.ninja,*.csproj,*.m4,*.rej,*.gmo,*.pc,*.omf,*.aux,*.tmp,*.po,*.vm*,*.nvram,*.rcore,*.swp,*.swap,lzo,litmain.sh,*.orig,.histfile.*,.xsession-errors*,*.map,*.so,*.a,*.db,*.qrc,*.ini,*.init,*.img,*.vdi,*.vbox*,vbox.log,*.qcow2,*.vmdk,*.vhd,*.vhdx,*.sql,*.sql.gz,*.ytdl,*.class,*.pyc,*.pyo,*.elc,*.qmlc,*.jsc,*.fastq,*.fq,*.gb,*.fasta,*.fna,*.gbff,*.faa,po,CVS,.svn,.git,_darcs,.bzr,.hg,CMakeFiles,CMakeTmp,CMakeTmpQmake,.moc,.obj,.pch,.uic,.npm,.yarn,.yarn-cache,__pycache__,node_modules,node_packages,nbproject,core-dumps,lost+found
exclude filters version=8
folders[$e]=$HOME/,/media/francois/Storage/
index hidden folders=true
only basic indexing=true
Comment 1 tagwerk19 2021-07-15 10:32:23 UTC
(In reply to francois072 from comment #0)
> 1. Configure baloo to index disk in /media
That means you should be able to change directory in Dolphin to
    /media/francois/Storage/
and start typing a filename for baloo to find. The Dolphin search dialog should look like:
    https://bugsfiles.kde.org/attachment.cgi?id=137169
    (Taken from in Bug 435119)
which means Dolphin is using baloo....

You can also do:
   baloosearch ...fileinyourmediafolders...
and see if it finds the file...

> 2. Open Kfind and select the disk indexed in step 1.
Here you've switched to using a different search tool...

> 3. Check "Use files index" box.
The "Use files index" means "You've created a file index with the 'updatedb'  program, look through this to find the files you want..."

> 4. Click on "Find" button.
> Having "Use files index" box unchecked does present results for disk in
> /media.
In this case KFind looks though your /media directory structure "there and then" and lists the matches.

> Having "Use files index" box checked does present results for user's home
> directory.
That implies (I think) that mlocate and updatedb are installed, just that updatedb isn't indexing your /media folders.
Comment 2 sg7e0f7m 2021-07-15 13:58:43 UTC
I see. I thought that Kfind also uses baloo. I did not realize that Kfind used mlocate for the database.