[frameworks-baloo] [Bug 384607] baloo_file_extractor SIGSEGV on some files

2017-09-25 Thread Erik Quaeghebeur
https://bugs.kde.org/show_bug.cgi?id=384607 --- Comment #9 from Erik Quaeghebeur --- Even if I couldn't find the file that causes the error for me, Igor provided sufficient material for a developer to seriously look at this issue. That is what needs to happen at

[frameworks-baloo] [Bug 384607] baloo_file_extractor SIGSEGV on some files

2017-09-25 Thread Igor Zhuravlov
https://bugs.kde.org/show_bug.cgi?id=384607 --- Comment #8 from Igor Zhuravlov --- Hmm, the command "balooctl disable" wipes dir ~/.local/share/baloo/ where indexed data are stored. So, if disabling and then enabling commands have fulfilled correctly then full reindexing must

[frameworks-baloo] [Bug 384607] baloo_file_extractor SIGSEGV on some files

2017-09-22 Thread Erik Quaeghebeur
https://bugs.kde.org/show_bug.cgi?id=384607 --- Comment #7 from Erik Quaeghebeur --- It seems all the candidates found by looking at the journal and balooctl monitor are already indexed[*]; I can't seem to find the culprit :-( [*] Skipping: /path/to/file.ext

[frameworks-baloo] [Bug 384607] baloo_file_extractor SIGSEGV on some files

2017-09-19 Thread Igor Zhuravlov
https://bugs.kde.org/show_bug.cgi?id=384607 --- Comment #6 from Igor Zhuravlov --- > “Baloo Index could not be opened”. It seems like baloo cannot reset to initial state. After "balooctl disable" ensure: - files ~/.config/baloo* - dir ~/.local/share/baloo/ - running baloo*

[frameworks-baloo] [Bug 384607] baloo_file_extractor SIGSEGV on some files

2017-09-18 Thread Erik Quaeghebeur
https://bugs.kde.org/show_bug.cgi?id=384607 --- Comment #5 from Erik Quaeghebeur --- (In reply to Igor Zhuravlov from comment #4) > 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

[frameworks-baloo] [Bug 384607] baloo_file_extractor SIGSEGV on some files

2017-09-17 Thread Igor Zhuravlov
https://bugs.kde.org/show_bug.cgi?id=384607 --- Comment #4 from Igor Zhuravlov --- 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:

[frameworks-baloo] [Bug 384607] baloo_file_extractor SIGSEGV on some files

2017-09-15 Thread Erik Quaeghebeur
https://bugs.kde.org/show_bug.cgi?id=384607 Erik Quaeghebeur changed: What|Removed |Added CC|

[frameworks-baloo] [Bug 384607] baloo_file_extractor SIGSEGV on some files

2017-09-12 Thread Igor Zhuravlov
https://bugs.kde.org/show_bug.cgi?id=384607 --- Comment #2 from Igor Zhuravlov --- Yet another file getting baloo_file_extractor to crash: > rpm -qa | egrep 'baloo|lmdb' baloo5-file-5.26.0-2.1.x86_64 baloo5-widgets-16.08.2-1.1.x86_64 baloo5-5.26.0-2.1.x86_64

[frameworks-baloo] [Bug 384607] baloo_file_extractor SIGSEGV on some files

2017-09-12 Thread Igor Zhuravlov
https://bugs.kde.org/show_bug.cgi?id=384607 --- Comment #1 from Igor Zhuravlov --- Created attachment 107829 --> https://bugs.kde.org/attachment.cgi?id=107829=edit this file crashes baloo_file_extractor -- You are receiving this mail because: You are watching all bug

[frameworks-baloo] [Bug 384607] baloo_file_extractor SIGSEGV on some files

2017-09-12 Thread Igor Zhuravlov
https://bugs.kde.org/show_bug.cgi?id=384607 Igor Zhuravlov changed: What|Removed |Added Summary|baloo_file_extractor|baloo_file_extractor