Plasma 5 -current: ~/.local/share/sddm/xorg-session.log takes up all remaining disk space
When I logged into my laptop this morning, I was greeted by a message that $HOME had 0 MB of disk space left. Digging into this, I eventually traced the culprit to ~/.local/share/sddm/xorg-session.log, which had grown to 104 GB. Tailing the file, I see these two messages repeated over and over:
Code:
org.kde.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid https://forums.gentoo.org/viewtopic-...99dec88eb28daa Too bad, I wanted to use it, but it has too many problems. Plasma 5 might be ready for prime time, but only if baloo is removed, IMO. I am purging it from my system now. Edit: also possibly related bug report: https://bugs.kde.org/show_bug.cgi?id=406868 |
I don't use baloo (I don't need it). My .config/baloofilerc contains
[Basic Settings] Indexing-Enabled=false I think that this disables baloo. |
Quote:
|
balooctl may offer some additional help.
Code:
$ balooctl Always something to keep things interesting! |
I tried baloo again today, this time removing ~/.local/share/baloo first and disabling indexing file content. It finishes in a matter of seconds now and doesn't blow up xorg-session.log. I will mark this as solved and perhaps modify my 2 cents to say that baloo is fine if file content indexing is disabled. It seems to be the file content indexing that was causing the really poor performance and probably also causing ~/.local/share/sddm/xorg-session.log to blow up.
|
Nice! I'm glad baloo is working out you you now.
|
All times are GMT -5. The time now is 06:59 PM. |