[frameworks-baloo] [Bug 392301] baloo_file_extractor logspam, invalid encoding

[Stefan Brüns]

https://bugs.kde.org/show_bug.cgi?id=392301

Stefan Brüns  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG

--- Comment #10 from Stefan Brüns  ---
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

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 392301] baloo_file_extractor logspam, invalid encoding

[soredake]

https://bugs.kde.org/show_bug.cgi?id=392301

soredake  changed:

   What|Removed |Added

 CC||fds...@krutt.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 392301] baloo_file_extractor logspam, invalid encoding

[Lukas Ba .]

https://bugs.kde.org/show_bug.cgi?id=392301

--- Comment #9 from Lukas Ba.  ---
(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.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 392301] baloo_file_extractor logspam, invalid encoding

[Stefan Brüns]

https://bugs.kde.org/show_bug.cgi?id=392301

--- Comment #8 from Stefan Brüns  ---
(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.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 392301] baloo_file_extractor logspam, invalid encoding

[Lukas Ba .]

https://bugs.kde.org/show_bug.cgi?id=392301

--- Comment #7 from Lukas Ba.  ---
Created attachment 112277
  --> https://bugs.kde.org/attachment.cgi?id=112277=edit
histfile_reduced

Here i am providing the result histfile_reduced.

file ~/.histfile
/home/user/.histfile: Non-ISO extended-ASCII text

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 392301] baloo_file_extractor logspam, invalid encoding

[Stefan Brüns]

https://bugs.kde.org/show_bug.cgi?id=392301

--- Comment #6 from Stefan Brüns  ---
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.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 392301] baloo_file_extractor logspam, invalid encoding

[Lukas Ba .]

https://bugs.kde.org/show_bug.cgi?id=392301

--- Comment #4 from Lukas Ba.  ---
(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.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 392301] baloo_file_extractor logspam, invalid encoding

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=392301

--- Comment #5 from Christoph Feck  ---
Reading more carefully, the issue is not the filenames, but the file contents,
so please ignore comment #3.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 392301] baloo_file_extractor logspam, invalid encoding

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=392301

--- Comment #3 from Christoph Feck  ---
Then fix these filenames using convmv. If they are invalid, the extractor has a
reason to complain.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 392301] baloo_file_extractor logspam, invalid encoding

[Lukas Ba .]

https://bugs.kde.org/show_bug.cgi?id=392301

--- Comment #2 from Lukas Ba.  ---
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 .

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 392301] baloo_file_extractor logspam, invalid encoding

[Stefan Brüns]

https://bugs.kde.org/show_bug.cgi?id=392301

Stefan Brüns  changed:

   What|Removed |Added

 CC||stefan.bruens@rwth-aachen.d
   ||e

--- Comment #1 from Stefan Brüns  ---
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.

-- 
You are receiving this mail because:
You are watching all bug changes.