https://bugs.kde.org/show_bug.cgi?id=384607
--- Comment #4 from Igor Zhuravlov <zhuravlov...@ya.ru> --- Erik, to identify problem file the following approach may be used: 1. stop baloo indexing by command: balooctl stop 2. reboot, log in 3. start baloo monitoring in separate console by command: balooctl monitor 4. start system journal monitoring in separate console by command: sudo journalctl -f 5. start baloo indexing again by command: balooctl start When journalctl will show baloo_file_extr error, then baloo hangs so the last 1-2-3 names displayed by baloo monitor are the best candidates to check by command: balooctl index -- You are receiving this mail because: You are watching all bug changes.
