Bug 447157

Summary:	baloo file extractor crash on chromium files
Product:	[Frameworks and Libraries] frameworks-baloo	Reporter:	Alis <aaa.soleimani>
Component:	Baloo File Daemon	Assignee:	baloo-bugs-null
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	nate, tagwerk19
Priority:	NOR
Version:	5.68.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	baloo file extractor backtrace

Description Alis 2021-12-18 10:03:54 UTC

Created attachment 144637 [details]
baloo file extractor backtrace

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. After Ubuntu log-in
2. Have Chromium installed
3. baloo file indexer will close unexpectedly.

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Linux 5.11.0-43-generic x86_64
(available in About System)
KDE Plasma Version: 5.18.7
KDE Frameworks Version: 5.12.8
Qt Version: 5.12.8

ADDITIONAL INFORMATION
It seems baloo file extractor will crash when reading some file on "snap/chromium/common/chromium/" most of the files that baloo failed to extract or read are in "snap/chromium/common/chromium/Default/".
On startup after removing the Chromium no crashing happens.
Backtrace is attached

Comment 1 tagwerk19 2021-12-19 08:59:14 UTC

(In reply to Alis from comment #0)
> ...  most of the files that baloo failed to
> extract or read are in "snap/chromium/common/chromium/Default/" ...
I see errors "Invalid encoding. Ignoring..." for a set of files, all called 00003.log. Seem to be LevelDB database files.

Checking the mime type:
    xdg-mime query filetype ...
gives:
    text/x-log
which isn't right. I don't get a crash though

Even though I get an "Invalid encoding" error (or warning?), I don't see the files appear in "balooctl failed"

Comment 2 tagwerk19 2021-12-19 09:04:42 UTC

I seem to be checking with a far more recent neon/baloo.

If you are really using 5.68.0, there's been things fixed, see Bug 431664

Comment 3 Nate Graham 2022-01-11 21:40:45 UTC

Indeed.