https://bugs.kde.org/show_bug.cgi?id=434565
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|REPORTED |CONFIRMED --- Comment #7 from [email protected] --- Expanding: https://bugs.kde.org/show_bug.cgi?id=406506#c18 SUMMARY Dolphin decides whether to populate tags, ratings and comments columns depending on the "Indexing-Enabled" value in .config/baloofilerc The information is taken from the filesystem extended attributes, not from the baloo index. STEPS TO REPRODUCE: Configure dolphin to display ratings, tags and comments columns Create a testfile and give it a rating and a tag getfattr -d file.txt # file: file.txt user.baloo.rating="4" user.xdg.tags="mytag" In order to prove that dolphin is reading the info direct from the extended attributes and not baloo, disable baloo and delete the index db: balooctl disable rm .local/shared/baloo/index Reboot, check .config/baloofilerc contains: Indexing-Enabled=false and that there are no baloo processes running. Open the folder with dolphin. There's no data displayed Close dolphin. Edit .config/baloofilerc to change: Indexing-Enabled=true Don't do anything else, so still no baloo processes or database OBSERVED RESULTS Check the folder with dolphin The tags and ratings columns are populated. EXPECTED RESULTS The "Indexing-Enabled" setting should not affect whether dolphin displays extended attribute data SYSTEM INFORMATION Neon Testing Plasma : 5.21.3 Frameworks: 5.81.0 Qt : 5.15.2 ADDITIONAL INFORMATION It seems that dolphin looks at .config/baloofilerc to see if indexing is enabled. If it is enabled, it populates the extended attribute data from the filesystem. If disabled it shows nothing. A small glitch in the grand scheme of things but will catch people who have had trouble with baloo and disabled it. (The information panel does however show the info) -- You are receiving this mail because: You are watching all bug changes.
