https://bugs.kde.org/show_bug.cgi?id=490928
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO |---
--- Comment #8 from tagwer...@innerjoin.org ---
(In reply to robakjoshua from comment #6)
> UPDATE2: I have mostly good news and some bad news. The good news is that
> excluding my ~/.steam and ~/.local/share/Steam folder seemed to resolve the
> constant high load writing that I was seeing before ...
I think Steam (and Wine) is a bit Terra Incognita for Baloo, they can drop
large structures of files onto the disc and possibly ones that Baloo does not
know how to decode (or avoid!).
> ... The only bad news is that Baloo will still write to the disk frequently,
> and
> alternates between indexing and idling indefinitely...
That could be considered normal. As an example, if you are indexing a log file,
Baloo will jump in and reindex it when it changes. Or if you are creating
temporary/work files, Baloo might be seeing those...
> ... Granted it's not
> anywhere near as bad as before, but after disabling the indexing of hidden
> files and folders, everything goes back to normal ...
Sounds good then...
> ... No more random constant
> writing to the disk at all. So it's probably another unknown that would need
> to be excluded. If there's any additional folders I should blacklist, please
> let me know. Otherwise, I am not as concerned about it since it doesn't look
> like a bug.
I think you have to keep watch on the "balooctl monitor" output or set up
logging (so you can then look through the journal). If you find a particular
file (or file type) repeatedly popping up, we can look deeper....
> Nevertheless, I can't be absolutely sure if the main problem is a bug with
> Baloo, or if Steam is just particularly bad for indexing. It certainly seems
> to be in a loop whenever it happens though. So I will keep this report open
> for the time being. I want to hear from others before I come to more of a
> conclusion.
That's fine, I'll set back to "Reported" for the time being.
--
You are receiving this mail because:
You are watching all bug changes.
