https://bugs.kde.org/show_bug.cgi?id=407972
Bug ID: 407972
Summary: baloo_file doesn't recover from baloo_file_extractor
crash
Product: frameworks-baloo
Version: 5.57.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: skierp...@gmail.com
Target Milestone: ---
SUMMARY
I have a file that triggers a crash in baloo_file_extractor in KDE Frameworks
5.57 and below (bug 404565). After this, baloo_file doesn't recover. It remains
stuck, never indexing another file until I kill it or balooctl disable then
balooctl enable. Meanwhile balooctl status reports nothing wrong.
STEPS TO REPRODUCE
1. Run balooctl monitor &
1. Trigger the crash (bug 405017 comment 4 points to a file that triggers it).
2. Let DrKonqi close the process.
3. Run balooctl status
4. Run ps
5. Try to recover
OBSERVED RESULT
After the baloo_file_extractor program exits, the baloo_file process continues
to run. But it never updates more files and can't spawn another
baloo_file_extractor.
$ balooctl status
Baloo File Indexer is running
Indexer state: Indexing file content
Indexed 27987 / 29422 files
Current size of index is 324.04 MiB
$ ps alx -w -w | grep baloo
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND
0 1000 1556 1 39 19 268871752 11968 x64_sy SNl ? 0:04
/usr/bin/baloo_file
0 1000 2086 1391 20 0 268916308 18376 x64_sy Ssl ? 0:06
/usr/libexec/baloorunner
...
Note: baloo_file_extractor has crashed.
$ balooctl monitor
Press ctrl+c to stop monitoring
File indexer is running
Indexing file content
Indexing: /path/to/problem/file/PANO_20190217_130422.vr.jpg
EXPECTED RESULT
baloo_file should recover from baloo_file_extractor crashing. balooctl status
should report there's a problem.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version: 5.57.0
Qt Version:
ADDITIONAL INFORMATION
balooctl stop then balooctl start has no effect. You have to kill the
baloo_file process, then balooctl start.
--
You are receiving this mail because:
You are watching all bug changes.
