The following message is repeated every second in the logs. >Mär 25 12:40:56 linux baloo_file_extractor[2094]: Invalid encoding. Ignoring "/home/user/.histfile" >Mär 25 12:40:56 linux kdeinit5[1063]: () >Mär 25 12:40:56 linux kdeinit5[1063]: ("/home/user/.histfile") >Mär 25 12:40:56 linux kdeinit5[1063]: () The file in question is the zsh history file, and can be read by text editor.
Happens if the file encoding is invalid according to your current locale. Please try: $> file ~/.histfile Should tell you if there are any invalid characters. You can also try $> sed -e 's/[-+^"!%#&$\\@_=:;.,/<>?* (){}a-zA-Z0-9]\?\[\?\]\?//g ' < ~/.histfile > ~/.histfile_reduced and then run check with e.g. hexdump -C or okteta what characters are still left.
The problem is not that a file has an invalid encoding, but that baloo_file_extractor complains about it. For some files, invalid encoding is a normal thing .
Then fix these filenames using convmv. If they are invalid, the extractor has a reason to complain.
(In reply to Christoph Feck from comment #3) > Then fix these filenames using convmv. If they are invalid, the extractor > has a reason to complain. No. I'm sure .histfile is an O.K. filename.
Reading more carefully, the issue is not the filenames, but the file contents, so please ignore comment #3.
You are contradicting yourself - "and can be read by text editor" - so it has some text encoding. I wanted to find out which codepoints are in there which are *not* valid, but unfortunately you are not providing this info.
Created attachment 112277 [details] histfile_reduced Here i am providing the result histfile_reduced. file ~/.histfile /home/user/.histfile: Non-ISO extended-ASCII text
(In reply to Lukas Ba. from comment #7) > Created attachment 112277 [details] > histfile_reduced > > Here i am providing the result histfile_reduced. > > file ~/.histfile > /home/user/.histfile: Non-ISO extended-ASCII text It contains invalid codepoints near the end.
(In reply to Stefan Brüns from comment #8) > (In reply to Lukas Ba. from comment #7) > > Created attachment 112277 [details] > > histfile_reduced > > > > Here i am providing the result histfile_reduced. > > > > file ~/.histfile > > /home/user/.histfile: Non-ISO extended-ASCII text > > It contains invalid codepoints near the end. Looks like zsh likes to add those codepoints to its history file. I also get that result with the default zsh config on kubuntu, so anyone installing zsh on kubuntu will see this.
zsh has no default history location, so you (or your distribution) has set HISTFILE explicitly. You also have enabled hidden file/directory indexing. There is not way baloo can guess this. If you want it excluded, either disable hidden file indexing, or exclude the file manually: $> balooctl config add excludeFilters .histfile