Created attachment 121323 [details] empty item in results SUMMARY When I use krunner and search for certain string, empty / null item is among results. It is always reproducible on one of my computers, but others work fine. Sometimes this empty item is image, sometimes folder, sometimes video. However it is consistent with search strings. Eg. when I search for "spo", it is always image. When I search for "a", it is always archive, when I search for "b" it is always video. If I disable plugin "Desktop Search", empty items do not appear in results. When I click empty item, I get error Malformed URL. I understand this is weird issue. Is there anything I could use to add more detailed information? Can I somehow call krunner query from console? STEPS TO REPRODUCE 1. Open krunner (I have Win key to open krunner) 2. Search for string spo OBSERVED RESULT Empty item appears. See attachment. EXPECTED RESULT No empty item. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION
Also I tried to clear baloo index, but that didn't help.
This seems to be somewhat fixed in Frameworks 5.60. I don't get so many empty items. However there are still some. Also I noticed that if I get empty result, now it's always folder, never file.
This can be related to bug 409257, which should be fixed in KF 5.60. Can you try the most recent version?
I did try it in KF 5.60 and already posted results. Is there newer version of KF?
Whoops, sorry. KF 5.60 is the most recent version for now. Have you tried clearing your index with 5.60? It should be fine.
I did try to clear index. I used balooctl disable balooctl purge balooctl enable and I still get corrupted items. Also just today I noticed that I have the same issue on another PC running Neon stable, fully updated (Plasma 5.16.3, KF 5.60.0, Qt 5.12.3) and clearing index didn't work as well. I will attach screenshot. Or maybe I didn't clear it right? Or do I need to start logout and log back in?
Created attachment 121725 [details] empty item on neon
*** Bug 358774 has been marked as a duplicate of this bug. ***
Is this still an issue on newer versions?
I tested on Plasma 5.19.5 and from time to time I see empty items. But it's nowhere near as common as before.
Can you please try to focus the empty item and check what the subtext says?
Doesn't say anything. And when I click on the item it gives me error Malformed URL. One bad result is folder and the other one is video. When I start krunner from shell, it doesn't print any error message, only warns about deprecated ToolButtonStyle.qml:196:13:
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/baloo/-/merge_requests/26
After update to KF 5.77.0 I started getting empty results also on my second notebook. Don't know if it's coincidence or not. Also noticed other problem - when I open Dolphin, "Modified Today" and "Modified Yesterday" return no items. Also 'baloosearch:/images/' returns no items.
Created attachment 134088 [details] empty item on arch
I just purged and recreated baloo index. This helped me with Dolphin issue, but empty results remain.
This might be an issue in KRunner itself, since I see the empty item no matter what the search results are. For example even if I enter 5+5, I get the expected calculator result, but also the empty item.
Same for me
Interesting enough, for me the empty file is categorized in the "Audio" group.
Temporarily, I can make it work if I disable baloo, kill baloorunner, purge the cache, then re-enable baloo (which needs to issue `balooctl enable` two times). It stops working after re-dis/enabling baloo, or after a reboot, though. baloo_file seems to crash, and baloosearch returns (an accurate number of) empty results too, so it's not krunner-specific. Unfortunately, my distro doesn't provide packages with debug symbols to give you a useful backtrace, so hopefully a dev can reproduce it. Also, drkonqi doesn't detect the crash, systemd-coredump does. Also, it might be important to add that downgrading the baloo package to 5.76 isn't enough to "fix" the issue.
(In reply to tgnff242 from comment #20) > Temporarily, I can make it work if I disable baloo, kill baloorunner, purge > the cache, then re-enable baloo (which needs to issue `balooctl enable` two > times). It stops working after re-dis/enabling baloo, or after a reboot, > though. > > baloo_file seems to crash, and baloosearch returns (an accurate number of) > empty results too, so it's not krunner-specific. Unfortunately, my distro > doesn't provide packages with debug symbols to give you a useful backtrace, > so hopefully a dev can reproduce it. Also, drkonqi doesn't detect the crash, > systemd-coredump does. > > Also, it might be important to add that downgrading the baloo package to > 5.76 isn't enough to "fix" the issue. I also have the same issue. Here is the backtrace from my crash of baloo_file: ``` #0 0x00007f257d8a6396 in ?? () from /usr/lib/liblmdb.so #1 0x00007f257d8a8efe in ?? () from /usr/lib/liblmdb.so #2 0x00007f257d8a9644 in ?? () from /usr/lib/liblmdb.so #3 0x00007f257d8a9c50 in mdb_get () from /usr/lib/liblmdb.so #4 0x00007f257ed802a5 in Baloo::IdFilenameDB::get (this=this@entry=0x7f257845c700, docId=<optimized out>, docId@entry=50665500102950405) at /usr/src/debug/baloo-5.77.0/src/engine/idfilenamedb.cpp:83 #5 0x00007f257ed7a2fc in Baloo::DocumentUrlDB::get (this=this@entry=0x7f257845c780, docId=docId@entry=50665500102950405) at /usr/src/debug/baloo-5.77.0/src/engine/documenturldb.cpp:171 #6 0x00007f257ed8b085 in Baloo::Transaction::documentUrl (this=<optimized out>, id=50665500102950405) at /usr/src/debug/baloo-5.77.0/src/engine/transaction.cpp:102 #7 0x00005645d02bf8e4 in operator() (id=<optimized out>, __closure=<optimized out>) at /usr/src/debug/baloo-5.77.0/src/file/indexcleaner.cpp:40 #8 std::__invoke_impl<bool, Baloo::IndexCleaner::run()::<lambda(quint64)>&, long long unsigned int> (__f=...) at /usr/include/c++/10.2.0/bits/invoke.h:60 #9 std::__invoke_r<bool, Baloo::IndexCleaner::run()::<lambda(quint64)>&, long long unsigned int> (__fn=...) at /usr/include/c++/10.2.0/bits/invoke.h:141 #10 std::_Function_handler<bool(long long unsigned int), Baloo::IndexCleaner::run()::<lambda(quint64)> >::_M_invoke(const std::_Any_data &, unsigned long long &&) (__functor=..., __args#0=<optimized out>) at /usr/include/c++/10.2.0/bits/std_function.h:291 #11 0x00007f257ed924ff in std::function<bool (unsigned long long)>::operator()(unsigned long long) const (__args#0=50665500102950405, this=0x7f2578c5a9c0) at /usr/include/c++/10.2.0/bits/std_function.h:622 #12 Baloo::WriteTransaction::removeRecursively(unsigned long long, std::function<bool (unsigned long long)> const&) (this=0x7ee570004e30, parentId=50665500102950405, shouldDelete=...) at /usr/src/debug/baloo-5.77.0/src/engine/writetransaction.cpp:159 #13 0x00007f257ed92557 in Baloo::WriteTransaction::removeRecursively(unsigned long long, std::function<bool (unsigned long long)> const&) ( this=0x7ee570004e30, parentId=50665500102950405, shouldDelete=...) at /usr/src/debug/baloo-5.77.0/src/engine/writetransaction.cpp:166 #14 0x00007f257ed92557 in Baloo::WriteTransaction::removeRecursively(unsigned long long, std::function<bool (unsigned long long)> const&) ( this=0x7ee570004e30, parentId=50665500102950405, shouldDelete=...) at /usr/src/debug/baloo-5.77.0/src/engine/writetransaction.cpp:166 #15 0x00007f257ed92557 in Baloo::WriteTransaction::removeRecursively(unsigned long long, std::function<bool (unsigned long long)> const&) ( this=0x7ee570004e30, parentId=50665500102950405, shouldDelete=...) at /usr/src/debug/baloo-5.77.0/src/engine/writetransaction.cpp:166 ``` The crash reporter didn't launch, but I found multiple crashes like this listed in the output of 'coredumpctl list'. I have compiled baloo with debug symbols, but please let me know if I should install debug symbols for any other package. The last line (#15) kept on getting repeated in gdb for some reason; not sure if this is important.
Another me too comment (meaning baloo_file dups core at startup and baloosearch shows empty lines) Some additional troubleshooting: balooctl disable balooctl purge balooctl enable After a while it seems that index is rebuilt correctly and baloosearch results are accurate but it does not survive a reboot. I tried the above but with an additional: balooctl disable _before rebooting_ and the baloosearch results survive the reboot (of course the indexer is not running. As soon as I: balooctl enable the following message appears: 61924499171376643 "/home/username/" renaming "username" to "" where username is my username, and baloosearch goes back to displaying empty lines and crashing. So it seems, and this might be speculation on my part, that a enabling baloo after a reboot corrupts the index.
Could this bug: https://bugs.kde.org/show_bug.cgi?id=430610 be a duplicate of this one?
Hmm, this has stopped happening for me. :/
Still happening for me. Downgrading to baloo 5.76 (from 5.77) fixes the issue as mentioned in the bug linked above.
This has become a bag of unrelated issues. It is no longer possible to say what any new comment refers to. Closing this. Please open a new report for *each* remaining issue.
Here's one: Bug 430891.