Created attachment 162061 [details] Folderview SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Search for a folder (in my example "WhiteSur-kde-master") OBSERVED RESULT no folders found EXPECTED RESULT Folder "WhiteSur-kde-master" SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230929 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.5-2.g6cf5261-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics
Created attachment 162062 [details] Search Result
Created attachment 162063 [details] Search Result 2
Another folder named x300 could be found via the search "x300"
Hello, just to be understand what is the reasons of this bug Could you please answer these questions for me 1- if the folder a hidden folder ? ( including one of the parents ) 2- is the one of its parent added as "Do not index" for baloo indexing under baloo setting in systemsettings 3- does your baloo somehow disabled or paused [ you can check under systemsettings ] 4- did you tried pausing baloo and purge its old data ( from konsole : balooctl purge ) and resume it and let the indexing finishes then restart dolphin and give a second try ?
Thanks for the bug report. I'm sorry we weren't able to get to this yet. There have been many fixes and improvements to Dolphin since this was reported, and this issue may have been fixed. Can you please re-test on your system with Dolphin 25.08.3 or later and let us know if you can still reproduce the problem? If you can, please set this report back to REPORTED. Thanks!
🐛🧹 ⚠️ 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!