[dolphin] [Bug 439438] New: Dolphin's search does not work (baloo enabled) when inside a linked folder

bugzilla_noreply at kde.org bugzilla_noreply at kde.org
Sat Jul 3 13:00:41 BST 2021


https://bugs.kde.org/show_bug.cgi?id=439438

            Bug ID: 439438
           Summary: Dolphin's search does not work (baloo enabled) when
                    inside a linked folder
           Product: dolphin
           Version: 21.04.2
          Platform: Neon Packages
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: search
          Assignee: dolphin-bugs-null at kde.org
          Reporter: dagobertram at mailbox.org
                CC: kfm-devel at kde.org
  Target Milestone: ---

SUMMARY
I tend to replace the standard folders in my home directory with links to
folders on other HDD's, such as Documents, Videos, Music and Pictures. I just
found out that baloo searches inside dolphin do not work, while being in the
linked folder.

Example:
The linked folder /home/<user>/Music links to a folder on a different HDD:
/media/<user>/HDD1/Music.
When I search for "interpret" inside of /home/<user>/Music it does neither
return /home/<user>/Music/Interpret nor /media/<user>/HDD1/Music/Interpret.
("baloosearch interpret" returns both, though, as does searching inside of
/home/<user>.)
When I search for "interpret" inside of /media/<user>/HDD1 it returns
/media/<user>/HDD1/Music/Interpret as expected.

STEPS TO REPRODUCE
1. replace the Music folder in your home directory with a link named "Music"
which links to a folder on another HDD
2. start search in Dolphin with CTRL+F and search for music in your home
directory
3. search for music after following the link to your "Music" by clicking on it

OBSERVED RESULT
2. returns search results
3. does not

EXPECTED RESULT
Works in both cases

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.2
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.3
Graphics Platform: X11

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the kfm-devel mailing list