If you select "From here" while in the user's home directory, search doesn't work: Even files that are obviously there and are visible in the directory before opening the search don't appear. This happens whether you search for filenames or content (I didn't check further options). Some more observations: * After a while, dolphin notifies the user that baloosearch died: "The process for the baloosearch protocol died unexpectedly." * balooctl status reports: "Baloo File Indexer is running.", Index looks healthy as well. * dolphin's terminal output contains: "Empty filename passed to function" on searching. * dolphin's terminal output sometimes contains: "org.kde.dolphin: slotUrlSelectionRequested: QUrl("file:///{{homedir}}/{{selected folder}}")" after selecting different folders (at somerandom point later?)
But searching explicitly in the home directory rather than "from here" does work?
Created attachment 115140 [details] Screenshot of search bar
I thought that selecting "From here (pholthaus)" is actually the explicit variant that searches in the current folder. The only other option is "Everywhere".
My apologies, I confused myself for a moment there! I meant, does it work when you click "Everywhere"?
Sorry, that has gone missing due to editing the original post. Yes, it works perfectly when you select "Everywhere".
Awesome, thanks for the info. BTW, we have a patch that should fix the issue: https://phabricator.kde.org/D15635
I think it isn't a Dolphin bug but a Baloo bug. If you try to force baloo to search an item (/home/user/foo) in a specific folder from terminal (baloosearch -d /home/user foo), it doesn't find anything, but, if you tell it to search that in the parent folder (baloosearch -d /home foo), it will find it. I don't know how to resolve this bug because I never worked on this project, but there's nothing wrong with Dolphin.
You are correct, and the patch is for Baloo. :)
Excuse me, my internet connection is horrible and I saw the comment too late. Anyway, I compiled the patched code, but the error persists.
Yari, it sounds like you have a different problem, then. I can confirm Patrick's issue but not yours. Would you file a new bug for it? Thanks!
Ok, there isn't any bug, my system's baloo simply didn't index my home directory before a certain date. So, I forced it to index again and it works. I don't know if Patrick's issue is the same that I had, but also unpatched dolphin now works well. Excuse me again but theese are my first approaches to KDE bugs community.
Not a problem, we've all been there. :)
Thank you Nate. Great to hear there is a patch already! Just because it may become useful: I tried to reproduce the bug on another system but was not successful. I don't know what could be the reason for that because both systems are more or less up-to-date although their update cycle is vastly different meaning that the other system did not get a lot of updates in between.
Git commit 95af521127c117c1aebf3a3881a86dc7422a2a11 by Jaime Torres Amate. Committed on 25/09/2018 at 17:20. Pushed by jtamate into branch 'master'. Use String to store UDS_USER and UDS_GROUP of String type. Summary: First crash I get after enabling Dr. Konqi for slaves. UDS_USER and UDS_GROUP are strings, not numbers, therefore I've got an assert (simplified): "udsField & KIO::UDSEntry::UDS_NUMBER", "udsentry.cpp", line=line@entry=113) Use the same methods to get those data as in file. Test Plan: Search an obvious file in $HOME, it is shown. Reviewers: dfaure, #baloo, #frameworks, ngraham Reviewed By: dfaure, #baloo, ngraham Subscribers: ngraham, broulik, kde-frameworks-devel Tags: #frameworks, #baloo Differential Revision: https://phabricator.kde.org/D15635 M +41 -2 src/kioslaves/search/kio_search.cpp M +6 -0 src/kioslaves/search/kio_search.h https://commits.kde.org/baloo/95af521127c117c1aebf3a3881a86dc7422a2a11
I'm on lastest update of user neon and find the issue still present. If i perform a dolphin search with the "From Here" selected, it fails to find any file and always shows no results. If I change the search option to "Your files", it finds the file. I find the same problem to be true from within baloosearch. When I use the -d option to baloosearch, it fails to find the same file that it found without the option. kishore@kishore-x403:~$ baloosearch AN4065 /home/kishore/Projects/Reference/Datasheets/ST/STM32F0 Reference Manual.pdf Elapsed: 2.35966 msecs kishore@kishore-x403:~$ baloosearch -d /home/kishore/Projects/Reference/Datasheets/ST AN4065 Elapsed: 0.329187 msecs kishore@kishore-x403:~$ baloosearch --version Baloo 5.86.0 kishore@kishore-x403:~$
(In reply to Kishore from comment #15) > I find the same problem to be true from within baloosearch. When I use the > -d option to baloosearch, it fails to find the same file that it found > without the option. I wonder what we are doing differently, I've found what may be the same PDF: https://www.waveshare.com/w/upload/d/d9/STM32F0-Reference.pdf Downloaded to: /home/test/Projects/Reference/Datasheets/ST/STM32F0 Reference Manual.pdf a straightforward folder tree, no symlinks. Both the tests work: $ baloosearch AN4065 /home/test/Projects/Reference/Datasheets/ST/STM32F0 Reference Manual.pdf Elapsed: 0,229862 msecs $ baloosearch -d /home/test/Projects/Reference/Datasheets/ST/ AN4065 /home/test/Projects/Reference/Datasheets/ST/STM32F0 Reference Manual.pdf Elapsed: 0,24483 msecs System is a Guest VM: KDE neon 5.22 Ext4 filesystem Plasma: 5.22.5 Frameworks: 5.86.0 Qt: 5.15.3 Kernel: 5.11.0-36-generic (64-bit)
Okay, 5 years later. This bug still hasn't been fixed. I was just about to file a bug.
Oh yeah, seems like it is a baloosearch bug. This still is true unfortunately $ baloosearch alpine-pi-script /home/jan/Downloads/alpine-pi-script elapsed: 1,29095 msec $ baloosearch -d Downloads alpine-pi-script Using canonical path '/home/jan/Downloads' for 'Downloads' eplapsed: 1,43824 msec
(In reply to jan.claussen10 from comment #18) > ... still is true unfortunately ... I've not been able to pin down an exact "as and when" it happens but there's been discussion in: https://bugs.kde.org/show_bug.cgi?id=474973#c22 was that you get the behaviour when you have a "doubled" $HOME entry in the .config/baloofilerc see: https://bugsfiles.kde.org/attachment.cgi?id=162267 Maybe attach your baloofilerc?
I don't seem to have a doubled entry in there it seems. http://ix.io/4JBh In the link you shared it says it only happens in the Downloads directory. This is not true. This maybe the case because there are not many files in there. If I search my Games folder, which is kind of large, it even segfaults. I am looking at the code, but I am a C++ noob and the Qt objects are a jungle to debug
(In reply to jan.claussen10 from comment #20) > In the link you shared it says it only happens in the Downloads directory. I think the focus in Bug 474973 was on the "Downloads", or "Scaricati", folder. I missed a trick not asking if the same issue was seen elsewhere :-/ > This is not true. This maybe the case because there are not many files in > there. If I search my Games folder, which is kind of large, it even > segfaults. Interesting. There are crashes with baloo_file_extractor, it has to deal with any and all sorts of file. Once indexed though things are more stable, don't get reports from baloosearch crashing (although I know Dolphin sometimes reports the search or tags protocol has crashed). If the command line baloosearch crashes, then most likely the index has been corrupted (*) I've tried all sorts of variations and not been able to find a way of duplicating the issue. Almost... There is the issue when you set up a symlink to a folder, say on your desktop, pointing to your Downloads folder. When you follow that link in Dolphin and search "from there" you are looking for files in "$HOME/Desktop/Downloads" and won't find any. I include this mention for completeness, you've said it's not an issue for you. Second, wild, possibility is you've somehow created a folder with the name "UTF-8" encoded. I don't know what might happen in this case. You say your Games folder? This is not a folder under Wine with Windows games? > I am looking at the code, but I am a C++ noob and the Qt objects are a jungle to debug The same for me.... *) There is a index "consistancy check" script, baloo-checkdb.py, but this is only practicable for "smaller" indexes...
I have several folder symlinks in my home folder that point to Nextcloud folders. Yes, the games folder contains some Wine games.
(In reply to jan.claussen10 from comment #22) > I have several folder symlinks in my home folder that point to Nextcloud > folders. > > Yes, the games folder contains some Wine games. Maybe related... https://bugs.kde.org/show_bug.cgi?id=474973#c27 At least I now have a system where I see the same issue...
Is this still happening? The main issue here was duplicated DocId's, https://bugs.kde.org/show_bug.cgi?id=474973#c27, that affected certain BTRFS based systems, openSUSE and later Fedora. The fix was rolled out autumn 2023 (see Bug 401863) but caused issues elsewhere. In all cases a "balooctl purge" and reindex fixed this issue. Subsequently there have been two fixes for systems using symlinks, the first clarifying the behaviour for balooctl, https://invent.kde.org/frameworks/baloo/-/merge_requests/126, and the second a fix for baloo, https://invent.kde.org/frameworks/baloo/-/merge_requests/226. The issue here was that if you moved to "folder" in Dolphin and searched "From here" for something, and "folder" was a symlink, you weren't going to find your "something".
I just stumbled upon this today. after the purge, it worked. I'm using kubuntu 25.04 (installation with 22.04) and ext4 filesystem. after the purge, the index was 4 times smaller. unfortunatly I don't have more details to add, since my bad index is already gone
(In reply to Marco Schmidlin from comment #25) > I'm using kubuntu 25.04 (installation with 22.04) and ext4 filesystem. after > the purge, the index was 4 times smaller. Thank you for posting. If you installed 22.04 and haven't reindexed, it could be that you were seeing the duplicate DocId's issue. All the same, if you do see any strange behaviour reappearing, it would be good to know. The "classic" test for duplicate Id's is to use baloosearch (could be baloosearch6) with the '-x' option to show the Id... $ baloosearch -x one-of-my-files.txt where you previously saw multiple hits for the file with different Id's.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.