https://bugs.kde.org/show_bug.cgi?id=437197
--- Comment #4 from Ian Proudler <i.proud...@oxon.org> --- (In reply to tagwerk19 from comment #3) > (In reply to Stefan Brüns from comment #2) > > Either something is rewriting .directory files recurrently ... > > ... or a change is detected although there is none. > Possible way forward (if focusing on the .directory files), is to install > inotify-tools and run > > inotifywait -mr ~ | grep .directory > > in one window and compare this to what baloo is indexing by running: > > balooctl monitor > > in a second... > > If I do this; running dolphin with per-folder settings enabled and pressing > Ctrl-H a few times to show and hide "hidden" files, iNotify shows a lock and > temporary file being created, the .directory file being deleted and the > tempfile renamed back to .directory. > > For me that seems sensible - and it's nice to see inotify showing the actions > > In parallel, balooctl monitor reindexes the .directory file each time I > change the config. > > So, for me, it's behaving. Do you see anything suspicious? > > Neon Unstable > Plasma: 5.22.80 > Frameworks: 5.83.0 > Qt: 5.15.2 I don't see anything wrong as such. Baloo is doing what it is supposed to do. It's just that it leaps into action immediately rather than waiting for the PC to idle. When baloo reads files it seems, on occasions, to slow down access to the HDD. I was just suggesting that it would be nice if baloo had a lower priority than the user when it came to accessing the disk. Although I'm not 100% sure, I feel that baloo's aggressive access to the disk is interfering with the operation of Octave. It certainly slows down the PC when I first login. Thanks to everyone for their input. -- You are receiving this mail because: You are watching all bug changes.
