Bug 430598 - baloo_file crashing
Summary: baloo_file crashing
Status: RESOLVED DUPLICATE of bug 430273
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.77.0
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Stefan Brüns
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-19 21:51 UTC by pipapo
Modified: 2020-12-19 22:06 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pipapo 2020-12-19 21:51:21 UTC
SUMMARY

First dolphin does not show any search results. However, in the console the output for different search terms with baloosearch produce different number of lines. But no results are printed.
After purging and restarting the indexing process erverything seems back to normal. But after logout and login again the indexing is not working. Starting baloo_file gives a segmentation error. Same results occurs with a new test account.

STEPS TO REPRODUCE
1. Purge and restart indexing with balooctl
2. Login and logout again

OBSERVED RESULT
No searching results printed. baloo_file is crashing.

EXPECTED RESULT
Display of search results.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.20.1
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

Output journald:
dbus-daemon	[session uid=1000 pid=3500] Activating service name='org.kde.runners.baloo' requested by ':1.200' (uid=1000 pid=13694 comm="/usr/bin/plasmashell " label="unconfined")
dbus-daemon	[session uid=1000 pid=3500] Successfully activated service 'org.kde.runners.baloo'
org.kde.runners.baloo	QFSFileEngine::open: No file name specified
org.kde.runners.baloo	QFSFileEngine::open: No file name specified
Comment 1 Stefan Brüns 2020-12-19 22:06:07 UTC

*** This bug has been marked as a duplicate of bug 430272 ***
Comment 2 Stefan Brüns 2020-12-19 22:06:46 UTC

*** This bug has been marked as a duplicate of bug 430273 ***