https://bugs.kde.org/show_bug.cgi?id=490928
robakjos...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |NOT A BUG
Status|REPORTED |RESOLVED
--- Comment #9 from robakjos...@gmail.com ---
UPDATE3: After some time to reflect, I don't believe it's a bug, but simply a
potential consequence of enabling a feature. In addition, I discovered that
some flatpaks installed on my system contributed to the latter problem of my
last update, so excluding my ~/.var helped reduce writes a bit as well.
(In reply to tagwerk19 from comment #8)
> (In reply to robakjoshua from comment #6)
> > ... 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....
Steam (and indirectly WINE as you pointed out) was the main culprit, however
checking the logs, I didn't see anything unusual. It just seemed to be a bad
file(s) that caused Baloo to freak out. Regardless, after updating my system
multiple times, I haven't been able to reproduce the main issue since then. It
might've just been a particular version of Baloo that caused it and is now
patched.
At this point, I don't know if there's anything more that I can add. I'm going
to mark this as resolved since I don't want to waste any more time from the
developers. Thank you to you all who helped.
--
You are receiving this mail because:
You are watching all bug changes.
