https://bugs.kde.org/show_bug.cgi?id=390730
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WAITINGFORINFO
Status|REPORTED |NEEDSINFO
CC| |tagwer...@innerjoin.org
--- Comment #1 from tagwer...@innerjoin.org ---
(In reply to Mahendra Tallur from comment #0)
> 1) install KDE Neon (or Manjaro KDE). In the installation wizard, choose a
> distinct ext4 data partition that is mounted under /data.
> 2) reboot, update the system
> 3) open the KDE control panel -> desktop search -> remove /data from the
> blacklist
Are you meaning "Manual Partitioning" and then creating a / and a /data
partition?
I have not seen this create an excluded folder in the Baloo config. The config
normally includes just your home directory (for Neon anyway, the rules are
different for Fedora, Maybe Manjaro does its own thing)
> 4) wait a little, and notice 1) baloo is idle 2) files from /data are not
> indexed
That would be the case on Neon, you won't have included /data in your locations
to index. It would need to be included with a "Start indexing a folder". Of
course I'm looking at version of Neon maybe 6 years newer than yours...
> 5) reboot
> 6) repeat 4
> 7) open the control panel again. Disable indexing completely. Re-enable it.
> 8) notice that the baloo process is not idle anymore and that files from
> /data are indeed being indexed
Not clear what's happening here.
If you still have this as an issue, maybe you can attach your
.config/baloofilerc configuration file - see what it looks like directly after
installation, see if it has changed after step 6 and again after step 8.
I can see that a running Baloo process *might* not recognise changes to the
config file but logging out and back in again should be the maximum needed to
get it to work.
--
You are receiving this mail because:
You are watching all bug changes.
