I just installed 15.4 on a new laptop.
Some 10GB of mails on /home, and about 100GB on a separate partition.
In the kde/plasma sys config tool , the search part is configured to index these two places.
But…
After more than 40 hours of uptime, the cpu and disk are still working and working. The laptop is warm as a saucepan before frying the eggs and the cpu breathes like a bull after a run up a hundred of hills.
htop shows baloo_file_extractor is running like a rat in a loop.
Killing baloo with a sigterm allows the latop to have some rest, and my laps to stop burning.
Any bug that i am not aware of ? Should i fix some config file somewhere to avoid global warming through baloo bugs ?
Are you trying to index the contents of files?
Are you trying to index files outside of your user’s home directory?
- For example:
> balooctl status
Baloo File Indexer is running
Indexer state: Idle
Total files indexed: 163,930
Files waiting for content indexing: 0
Files failed to index: 0
Current size of index is 108.79 MiB
>
> balooctl indexSize
File Size: 108.79 MiB
Used: 63.34 MiB
PostingDB: 10.40 MiB 16.423 %
PositionDB: 11.41 MiB 18.020 %
DocTerms: 10.00 MiB 15.794 %
DocFilenameTerms: 9.38 MiB 14.813 %
DocXattrTerms: 0 B 0.000 %
IdTree: 2.66 MiB 4.194 %
IdFileName: 10.54 MiB 16.645 %
DocTime: 6.80 MiB 10.731 %
DocData: 0 B 0.000 %
ContentIndexingDB: 0 B 0.000 %
FailedIdsDB: 0 B 0.000 %
MTimeDB: 2.14 MiB 3.380 %
>
No global warming through baloo running on host erlangen:
[FONT=monospace]karl@erlangen:~> LANG=C balooctl status
Baloo File Indexer is not running
Total files indexed: 573,236
**Files waiting for content indexing: 112,083**
Files failed to index: 0
**Current size of index is 21.89 GiB **
karl@erlangen:~> [/FONT]
System load is moderate:
karl@erlangen:~> w
19:28:53 up 1:22, 4 users, load average: 1,31, 1,21, 1,13
USER TTY VON LOGIN@ IDLE JCPU PCPU WHAT
karl tty7 :0 18:06 1:22 m 2.89 s 0.07 s /usr/bin/startplasma-x11
karl pts/0 :0 18:06 1:22 m 0.00 s 1.22 s /usr/bin/kded5
karl pts/1 :0 18:06 1:21 m 0.30 s 0.18 s /bin/bash
karl pts/2 2001:a62:38d:610 19:24 0.00 s 0.13 s 0.00 s w
karl@erlangen:~>
As always your mileage may vary.
BTW: From top
**6828 karl 39 19 0.252t 0.018t 0.016t R 97.33 59.63 88:12.47 baloo_file_extr **
**
[FONT=monospace]
--christophe@mamachine 23:24:53 ~]** LANG=C balooctl status
Baloo File Indexer is running
Indexer state: Idle
Total files indexed: 297,410
Files waiting for content indexing: 79,670
Files failed to index: 0
Current size of index is 39.16 GiB
Well, it’s been indexing for two days, now. It’s a bit worrying. But, i will be patient, then…
[/FONT]
erlangen is done:
karl@erlangen:~> LANG=C balooctl status
Baloo File Indexer is running
Indexer state: Indexing new files
Total files indexed: 573,503
Files waiting for content indexing: 0
Files failed to index: 0
Current size of index is 28.87 GiB
karl@erlangen:~> balooctl indexSize
File Size: 28,87 GiB
Used: 1,09 GiB
PostingDB: 2,38 GiB 217.408 %
PositionDB: 3,68 GiB 336.172 %
DocTerms: 2,90 GiB 265.307 %
DocFilenameTerms: 43,95 MiB 3.923 %
DocXattrTerms: 0 B 0.000 %
IdTree: 8,09 MiB 0.722 %
IdFileName: 47,81 MiB 4.268 %
DocTime: 22,38 MiB 1.997 %
DocData: 3,22 MiB 0.288 %
ContentIndexingDB: 4,00 KiB 0.000 %
FailedIdsDB: 0 B 0.000 %
MTimeDB: 12,35 MiB 1.102 %
karl@erlangen:~>
But it’s not a laptop. It’s a desktop configured for content creation:
erlangen:~ # inxi -MCD
Machine:
Type: Desktop Mobo: Micro-Star model: B550-A PRO (MS-7C56) v: 2.0
serial: 07C5622_L41E321872 UEFI: American Megatrends LLC. v: A.90
date: 03/17/2022
CPU:
Info: 6-core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP cache:
L2: 3 MiB
Speed (MHz): avg: 2825 min/max: 2200/4650 cores: 1: 2200 2: 2200 3: 3700
4: 2200 5: 2200 6: 3700 7: 3700 8: 2200 9: 2200 10: 2200 11: 3700 12: 3700
Drives:
Local Storage: total: 3.64 TiB used: 1.8 TiB (49.4%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 2TB
size: 1.82 TiB
ID-2: /dev/sdc vendor: Crucial model: CT2000BX500SSD1 size: 1.82 TiB
erlangen:~ #
It stays quiet and cool while indexing. Users will never be able to tell whether indexer is idle or running.
I would like to thank all of you for your answers.
But…
I have waited some time to give baloo a chance, but, after some days, it keeps on saturating 1 of the 8 cpus, and the fan still blows continuously…
**--christophe@mamachine 14:56:49 ~]** LANG=C balooctl status
Baloo File Indexer is running
Indexer state: Idle
Total files indexed: 366,975
Files waiting for content indexing: 11
Files failed to index: 100
Current size of index is 39.21 GiB
Among the unindexed files are files like .bash_history or some firefox cache files :
[FONT=monospace]**--christophe@dedion 14:56:15 ~]** LANG=C balooctl failed
The following files could not be indexed:
/home/christophe/.bash_history
/home/christophe/.local/share/sddm/xorg-session.log
/home/christophe/.cache/mesa_shader_cache/index
/home/christophe/.local/share/baloo/index
/home/christophe/.config/pulse/137ca30762ca466aa972b562cf4d72-device-volumes.tdb
/home/christophe/.config/pulse/137ca30762ca466aa972b562cf4d72-stream-volumes.tdb
/home/christophe/.local/share/kactivitymanagerd/resources/database
/home/christophe/.config/gtk-3.0/colors.css
/home/christophe/.config/libaccounts-glib/accounts.db-shm
/home/christophe/.local/share/kscreen/outputs/b79d3a125a71d7fe03545f3df98538
/home/christophe/.local/share/kscreen/438185af8fefa118d3d5002cecb2c3
/home/christophe/.config/pulse/137ca30762ca466aa972b562cf4d72-default-sink
/home/christophe/.config/pulse/137ca30762ca466aa972b562cf4d72-default-source
/home/christophe/.local/share/openSUSE/org.opensuse.opensuse_welcome/QtWebEngine/Default/Session Storage/000003.log
/home/christophe/.cache/icon-cache.kcache
/home/christophe/.cache/plasma_theme_oxygen_v5.90.0.kcache
/home/christophe/.config/htop/htoprc
/home/christophe/.local/share/kded5/keyboard/session/layout_memory.xml
/home/christophe/.gkrellm2/data/net/eth0
/home/christophe/.gkrellm2/data/net/ppp0
/home/christophe/.gkrellm2/data/net/wlan0
/home/christophe/.gkrellm2/sensor-config
/home/christophe/.mozilla/firefox/d292mh75.default-release/.parentlock
/home/christophe/.mozilla/firefox/d292mh75.default-release/cookies.sqlite
/home/christophe/.mozilla/firefox/d292mh75.default-release/storage.sqlite
/home/christophe/.mozilla/firefox/d292mh75.default-release/storage/permanent/chrome/idb/3870112724rsegmnoittet-es.sqlite
/home/christophe/.mozilla/firefox/d292mh75.default-release/permissions.sqlite
/home/christophe/.mozilla/firefox/d292mh75.default-release/webappsstore.sqlite
/home/christophe/.mozilla/firefox/d292mh75.default-release/content-prefs.sqlite
/home/christophe/.mozilla/firefox/d292mh75.default-release/places.sqlite
/home/christophe/.mozilla/firefox/d292mh75.default-release/datareporting/glean/db/data.safe.bin
/home/christophe/.mozilla/firefox/d292mh75.default-release/favicons.sqlite
/home/christophe/.mozilla/firefox/d292mh75.default-release/storage/permanent/chrome/idb/2918063365piupsah.sqlite
/home/christophe/.cache/mozilla/firefox/d292mh75.default-release/cache2/entries/10C2DF682B4716DE9C09B841A80149E038C67573
/home/christophe/.cache/mozilla/firefox/d292mh75.default-release/cache2/entries/8FE18CE9297E2816C6DD43614FE64D0B6CE882B1
/home/christophe/.cache/mozilla/firefox/d292mh75.default-release/cache2/entries/EA1E3132006CB34CB9058E6891C35B731B9C4D9B
/home/christophe/.cache/mozilla/firefox/d292mh75.default-release/cache2/entries/8EC9FF17792BAA98EA88EC1CBDD9089F3384F606
/home/christophe/.cache/mozilla/firefox/d292mh75.default-release/cache2/entries/133BA7433E70D01A860D4F2682F34095B122FF42
.....
[/FONT]
Isn’t it weird ?
No. It ain’t weird. It’s your configuration.
> LANG=C balooctl config list hidden
no
>
> LANG=C balooctl config list contentIndexing
no
>
> LANG=C balooctl config list includeFolders
/home/???/
>
> LANG=C balooctl config list excludeFolders
>
> LANG=C balooctl config list excludeFilters
.pch
*.pyo
cmake_install.cmake
*.vm*
.svn
*.rcore
*.moc
.git
*.class
*.lo
litmain.sh
*.csproj
*.pc
CMakeCache.txt
*.fasta
*.orig
nbproject
confdefs.h
.moc
*.gmo
.uic
CVS
.npm
*.jsc
.yarn-cache
*.qmlc
CTestTestfile.cmake
node_packages
*.omf
*.pyc
config.status
__pycache__
.xsession-errors*
autom4te
libtool
*.qrc
.bzr
*.init
CMakeTmpQmake
*.rej
*.aux
po
*.faa
*.map
node_modules
*.elc
conftest
*~
.obj
*.so
*.po
*.m4
CMakeTmp
*.fastq
*.tmp
CMakeFiles
Makefile.am
*.swap
core-dumps
*.gb
ui_*.h
qrc_*.cpp
*.la
*.o
moc_*.cpp
*.ini
.hg
*.fna
confstat
.histfile.*
*.gbff
lost+found
*.db
*.a
*.nvram
*.part
*.fq
_darcs
lzo
.yarn
*.loT
*.gcode
.ninja_deps
.ninja_log
build.ninja
*.swp
*.img
*.vdi
*.vbox*
vbox.log
*.qcow2
*.vmdk
*.vhd
*.vhdx
*.sql
*.sql.gz
*.ytdl
>
> LANG=C balooctl config list excludeMimetypes
text/vnd.trolltech.linguist
text/x-assembly
application/json-patch+json
text/csx
application/geo+json
application/pgp-encrypted
text/x-lua
text/jsx
text/css
text/x-objsrc
text/x-qml
application/javascript
text/x-copying
text/x-sed
application/x-python
application/x-perl
application/x-java
text/x-yacc
text/x-erlang
text/x-cmake
application/x-sh
text/x-c++src
application/x-csh
application/x-awk
text/x-scheme
application/json
text/x-haskell
application/x-php
text/x-python
text/x-pascal
text/x-fortran
application/x-javascript
text/x-csrc
text/asp
application/x-cgi
application/ld+json
text/x-readme
application/x-ipynb+json
text/x-chdr
text/x-ruby
text/x-c++hdr
application/xml
text/x-java
>
I, do not index hidden files, do not index content, have no Folders excluded, have only the default list of exclude Filters and, have only the default list of excluded MIME types …
dcurtisfra , thanks for your nice input.
So i toggled the hidden files indexing to off.
But, no results. There is still 1 of the 8 cpus at 100%…
Runing " LANG=C balooctl monitor " shows that baloo is looping on the same files over and over again…
What to do ?
By the way, why should i not index hidden files ?
Isn’t it supposed to be a feature of the baloo ?
I think the problem is somewhere else…
Anyone knows where ?
First of all, thank you for staying with us and, putting up with our efforts to help you.
[HR][/HR]Please note that, Baloo is currently stable but, that wasn’t always the case – I have a script which cleaned up the Baloo configuration and database every few days – that script, thank goodness, was last needed in the year 2019 …
- First, stop Baloo – “/usr/bin/balooctl stop”
- Then, remove the Baloo index files located in ‘~/.local/share/baloo/’.
- Then, check the contents of ‘~/.config/baloofilerc’ and “~/.config/baloofileinformationrc”
- If the configuration seems to be OK, check where Baloo is present in the ‘~/.config/’ files –
[INDENT=2]On this machine, Baloo is mentioned in the configuration files as follows
[/INDENT]
> grep -Ri 'baloo' .config/*
.config/kded5rc:[Module-baloosearchmodule]
.config/krunnerrc:baloosearchEnabled=false
.config/QtProject/qtlogging.ini:org.kde.baloo.widgets.info=false
.config/QtProject/qtlogging.ini:org.kde.baloo.widgets.debug=false
.config/QtProject/qtlogging.ini:org.kde.baloo.widgets.warning=false
.config/QtProject/qtlogging.ini:org.kde.baloo.widgets.critical=false
.config/QtProject/qtlogging.ini:org.kde.baloo.info=false
.config/QtProject/qtlogging.ini:org.kde.baloo.debug=false
.config/QtProject/qtlogging.ini:org.kde.baloo.warning=false
.config/QtProject/qtlogging.ini:org.kde.baloo.critical=false
.config/QtProject/qtlogging.ini:org.kde.baloo.engine.info=false
.config/QtProject/qtlogging.ini:org.kde.baloo.engine.debug=false
.config/QtProject/qtlogging.ini:org.kde.baloo.engine.warning=false
.config/QtProject/qtlogging.ini:org.kde.baloo.engine.critical=false
>
- Then, restart Baloo.
Thank you for your answer.
So i realized that something went wrong and decided to reset the baloo.
The stop command is :
/usr/bin/balooctl disable
I removed the Baloo index files located in ‘~/.local/share/baloo/’
And i restarted the index process with the the kde graphic interface.
Until now, more than 30 hours after, the indexing process is still in progress, with about 25% of the volume idexed. NB: there are more than 230GB to index, so that might be the reason why it is so long. But, unlike the previous indexing process there are no baloo at 100% cpu, and no files failed to index.
Let’s be patient and see if, this time, it will succeed.
BTW, the reason of the previous failure might also be my savage killing of some baloo process through an unexpected sigterm.
Wait and see.
May well be a slow disk drive –
- Please check the SMART status of the drive (or drives) involved – you may well have a disk which is about to expire …
Content indexing can be a stress test. One run on some 100 GB started at Aug 23 12:39:20 and ended at [FONT=monospace]Aug 23 20:53:02:
[/FONT]
karl@erlangen:~> du -hd0
126G .
karl@erlangen:~>
baloo_file_extractor uses all RAM available, but frees some of it after succeeding:
[FONT=monospace]karl@erlangen:~> LANG=C free -h
total used free shared buff/cache available
Mem: 29Gi 3.8Gi 7.5Gi 55Mi 18Gi 25Gi
Swap: 0B 0B 0B
karl@erlangen:~>
[/FONT]
[FONT=monospace][FONT=monospace]karl@erlangen:~> LANG=C balooctl status
Baloo File Indexer is running
Indexer state: Idle
Total files indexed: 208,419
Files waiting for content indexing: 0
Files failed to index: 0
Current size of index is 24.70 GiB
karl@erlangen:~> [/FONT][/FONT]
karl@erlangen:~> balooctl indexSize
**File Size: 24,70 GiB
Used: 1,28 GiB **
PostingDB: 587,26 MiB 44.660 %
PositionDB: 1,57 GiB 122.340 %
DocTerms: 3,08 GiB 239.906 %
DocFilenameTerms: 15,79 MiB 1.201 %
DocXattrTerms: 0 B 0.000 %
IdTree: 2,84 MiB 0.216 %
IdFileName: 17,30 MiB 1.316 %
DocTime: 9,48 MiB 0.721 %
DocData: 9,37 MiB 0.713 %
ContentIndexingDB: 0 B 0.000 %
FailedIdsDB: 0 B 0.000 %
MTimeDB: 5,57 MiB 0.423 %
karl@erlangen:~>
Index file is huge, but usage is only a few percent.
Thanks. That’s a good question.
**--root@mamachine 09:21:27 /home/christophe]** smartctl -a /dev/nvme0
smartctl 7.2 2021-09-14 r5237 [x86_64-linux-5.14.21-150400.24.18-default] (SUSE RPM)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: Samsung SSD 980 PRO 500GB
Serial Number: S5GYNF0R322405E
Firmware Version: 2B2QGXA7
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Total NVM Capacity: 500 107 862 016 [500 GB]
Unallocated NVM Capacity: 0
Controller ID: 6
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 500 107 862 016 [500 GB]
Namespace 1 Utilization: 96 579 633 152 [96,5 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 002538 b311b17dc6
Local Time is: Fri Aug 26 09:21:54 2022 CEST
Firmware Updates (0x16): 3 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0057): Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp
Log Page Attributes (0x0f): S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size: 128 Pages
Warning Comp. Temp. Threshold: 82 Celsius
Critical Comp. Temp. Threshold: 85 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 8.49W - - 0 0 0 0 0 0
1 + 4.48W - - 1 1 1 1 0 200
2 + 3.18W - - 2 2 2 2 0 1000
3 - 0.0400W - - 3 3 3 3 2000 1200
4 - 0.0050W - - 4 4 4 4 500 9500
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 62 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 1%
Data Units Read: 1 238 869 944 [634 TB]
Data Units Written: 26 151 668 [13,3 TB]
Host Read Commands: 4 585 367 005
Host Write Commands: 1 034 371 674
Controller Busy Time: 7 072
Power Cycles: 39
Power On Hours: 156
Unsafe Shutdowns: 8
Media and Data Integrity Errors: 0
Error Information Log Entries: 0
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 62 Celsius
Temperature Sensor 2: 76 Celsius
Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged
[FONT=monospace]**--root@mamachine 09:22:01 /home/christophe]** smartctl -a /dev/nvme1
smartctl 7.2 2021-09-14 r5237 [x86_64-linux-5.14.21-150400.24.18-default] (SUSE RPM)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: Sabrent Rocket Q
Serial Number: 203E0714141500125008
Firmware Version: RKT30Q.3
PCI Vendor/Subsystem ID: 0x1987
IEEE OUI Identifier: 0x6479a7
Total NVM Capacity: 1 000 204 886 016 [1,00 TB]
Unallocated NVM Capacity: 0
Controller ID: 1
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 1 000 204 886 016 [1,00 TB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 6479a7 4b50504430
Local Time is: Fri Aug 26 09:22:07 2022 CEST
Firmware Updates (0x12): 1 Slot, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005d): Comp DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x08): Telmtry_Lg
Maximum Data Transfer Size: 512 Pages
Warning Comp. Temp. Threshold: 75 Celsius
Critical Comp. Temp. Threshold: 80 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 5.55W - - 0 0 0 0 0 0
1 + 4.49W - - 1 1 1 1 0 0
2 + 3.97W - - 2 2 2 2 0 0
3 - 0.0490W - - 3 3 3 3 2000 2000
4 - 0.0018W - - 4 4 4 4 25000 25000
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 2
1 - 4096 0 1
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 29 Celsius
Available Spare: 100%
Available Spare Threshold: 5%
Percentage Used: 0%
Data Units Read: 1 351 350 [691 GB]
Data Units Written: 466 331 [238 GB]
Host Read Commands: 2 675 670
Host Write Commands: 279 327
Controller Busy Time: 18
Power Cycles: 29
Power On Hours: 274
Unsafe Shutdowns: 3
Media and Data Integrity Errors: 0
Error Information Log Entries: 160
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Error Information (NVMe Log 0x01, 16 of 63 entries)
Num ErrCount SQId CmdId Status PELoc LBA NSID VS
0 160 0 0x1011 0x4004 0x028 0 0 -
[/FONT]
The baloo indexing has been runing for about 5 days, now, and it is stuck at 35% indexing, according to the kde systemsettings utility.
The first disk, the samsung /dev/nvme0 , is always active, according to the full graphic on the gkrellm utility. And we see that the temperature is above 60°C, and the other one below 30°C .
And htop shows baloo is always active.
Definitely !
More than 4 days of indexing and still only 35% of the content is indexed.
Plus : it is stuck at 35% since yesterday…
In the previous install, i always disabled indexing because it was too hungry. Decided to give it a try for 15.4 on a new laptop with a fast cpu and a lot of RAM. But, if it takes weeks to index my content, i may give up…
Live Tumbleweed works like a charm:
**notebook:~ #** inxi -zFm
**System:**
**Kernel:** 5.19.2-1-default **arch:** x86_64 **bits:** 64 **Console:** pty pts/3 **Distro:** openSUSE Tumbleweed
20220823
**Machine:**
**Type:** Laptop **System:** LENOVO **product:** 21A4 **v:** ThinkBook 15 G3 ACL **serial:** <filter>
**Mobo:** LENOVO **model:** LNVNB161216 **v:** SDK0T76530 WIN **serial:** <filter> **UEFI:** LENOVO
**v:** GQCN29WW(V1.15) **date:** 11/04/2021
**Battery:**
**ID-1:** BAT1 **charge:** 44.9 Wh (99.8%) **condition:** 45.0/45.0 Wh (100.0%)
**Memory:**
**RAM:****total:** 13.48 GiB **used:** 1.43 GiB (10.6%)
**Array-1:****capacity:** 64 GiB **slots:** 2 **EC:** None
**Device-1:** DIMM 0 **type:** DDR4 **size:** 8 GiB **speed:** 3200 MT/s
**Device-2:** DIMM 0 **type:** DDR4 **size:** 8 GiB **speed:** 3200 MT/s
**CPU:**
**Info:** 8-core **model:** AMD Ryzen 7 5700U with Radeon Graphics **bits:** 64 **type:** MT MCP **cache:**
**L2:** 4 MiB
**Speed (MHz):****avg:** 1400 **min/max:** 1400/4370 **cores:****1:** 1400 **2:** 1400 **3:** 1400 **4:** 1400 **5:** 1400
**6:** 1400 **7:** 1400 **8:** 1400 **9:** 1400 **10:** 1400 **11:** 1400 **12:** 1400 **13:** 1400 **14:** 1400 **15:** 1400 **16:** 1400
**Graphics:**
**Device-1:** AMD Lucienne **driver:** amdgpu **v:** kernel
**Device-2:** IMC Networks Integrated Camera **type:** USB **driver:** uvcvideo
**Display:** x11 **server:** X.org **v:** 1.21.1.4 **with:** Xwayland **v:** 22.1.3 **driver:****X:**
**loaded:** modesetting **unloaded:** fbdev,vesa **gpu:** amdgpu **tty:** 118x51 **resolution:** 1920x1080
**Message:** GL data unavailable in console for root.
**Audio:**
**Device-1:** AMD Renoir Radeon High Definition Audio **driver:** snd_hda_intel
**Device-2:** AMD ACP/ACP3X/ACP6x Audio Coprocessor **driver:** N/A
**Device-3:** AMD Family 17h/19h HD Audio **driver:** snd_hda_intel
**Sound Server-1:** ALSA **v:** k5.19.2-1-default **running:** yes
**Sound Server-2:** PipeWire **v:** 0.3.56 **running:** yes
**Network:**
**Device-1:** Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet **driver:** r8169
**IF:** eno1 **state:** down **mac:** <filter>
**Device-2:** MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter **driver:** mt7921e
**IF:** wlp4s0 **state:** up **mac:** <filter>
**Bluetooth:**
**Device-1:** Foxconn / Hon Hai Wireless_Device **type:** USB **driver:** btusb
**Report:** rfkill **ID:** hci0 **rfk-id:** 8 **state:** down **bt-service:** not found **rfk-block:****hardware:** no
**software:** no **address:** see --recommends
**Drives:**
**Local Storage:****total:** 506.76 GiB **used:** 344.1 MiB (0.1%)
**ID-1:** /dev/nvme0n1 **vendor:** Samsung **model:** MZALQ512HBLU-00BL2 **size:** 476.94 GiB
**ID-2:** /dev/sda **type:** USB **vendor:** Intenso **model:** Ultra Line **size:** 29.82 GiB
**Partition:**
**ID-1:** / **size:** 28.3 GiB **used:** 344.1 MiB (1.2%) **fs:** overlay **source:** ERR-102
**Swap:**
**Alert:** No swap data was found.
**Sensors:**
**System Temperatures:****cpu:** 39.9 C **mobo:** N/A **gpu:** amdgpu **temp:** 38.0 C
**Fan Speeds (RPM):** N/A
**Info:**
**Processes:** 315 **Uptime:** 20h 4m **Init:** systemd **Shell:** Bash **inxi:** 3.3.20
**notebook:~ #**
Why do you need to index the content of files on a Laptop?
Does the Laptop installation use the default Btrfs filesystem?
- Please note the text related to Btrfs in the ArchWiki related to Baloo – <https://wiki.archlinux.org/title/Baloo>.
- Please also note the issue around the indexing of content of KDE Plasma Vault files …
@ Christophe_deR
I’ve refrained from commenting on this thread so far, but will now make the suggestion that you take a serious look at “recoll” https://www.lesbonscomptes.com/recoll/ (you can find it in the "KDE:Extra repository) as an alternative to baloo.
It is fast, highly configurable, and very well supported by it’s primary author. I use it on all my machines, including a (relatively low spec) laptop, having kicked baloo into the long grass a long time ago.
With apologies to the OP for answering a query directed to them.
Possibly for the same reason as I index files on a laptop - I often can’t offhand recall which document contains the text I’m looking for.
(Partial) index statistics for my laptop: https://paste.opensuse.org/view/raw/37f6f268 - I’m just unable to memorise all that… 
OK – your information confirms what I’ve suspected for a while now – Baloo is OK for indexing files but, indexing content is something I’ve avoided for some time – maybe it’s time to investigate the thing again but, please be aware that my User directories are all on XFS filesystems …