https://bugs.kde.org/show_bug.cgi?id=476479
--- Comment #11 from tagwer...@innerjoin.org ---
(In reply to tagwerk19 from comment #9)
> ... it's something of a relief that Ext4 over LUKS2 did give a stable
> device number. I think now a question of patience, watching with "balooctl
> monitor" (and
https://bugs.kde.org/show_bug.cgi?id=476479
--- Comment #10 from tagwer...@innerjoin.org ---
(In reply to David Kredba from comment #7)
> Are there sanity/health checks for the index file BTW?
Sorry, I missed that one. Yes. Igor Poboiko has a
baloo-checkdb.py
script here:
https://bugs.kde.org/show_bug.cgi?id=476479
--- Comment #9 from tagwer...@innerjoin.org ---
(In reply to David Kredba from comment #8)
> ... it asks for Computer restart after enabling it (at least in GUI of
> Settings) ...
No a reboot is not needed, a restart of the Baloo process is sufficient.
https://bugs.kde.org/show_bug.cgi?id=476479
--- Comment #8 from David Kredba ---
(In reply to tagwerk19 from comment #6)
You were right, it is doubled. I do have 363696 regular files in home folder.
(cd && find . \( ! -regex '.*/\..*' \) -type f | wc -l)
Stopped, purged, logged off/on,
https://bugs.kde.org/show_bug.cgi?id=476479
--- Comment #7 from David Kredba ---
Both the mdb_copy and mdb_stat commands understand the index file structure and
Baloo continues to index content of my files
without complaining so I think its structure was not damaged by the crash. I
will let it
https://bugs.kde.org/show_bug.cgi?id=476479
--- Comment #6 from tagwer...@innerjoin.org ---
> ... Crash ...
I think you are off in the wildlands with:
> Current size of index is 67.41 GiB
and
> Memory: 62.7 GiB of RAM
I'd be 95% sure that the root cause is reindexing (possibly historically,
https://bugs.kde.org/show_bug.cgi?id=476479
Nate Graham changed:
What|Removed |Added
Severity|normal |crash
CC|
https://bugs.kde.org/show_bug.cgi?id=476479
--- Comment #5 from tagwer...@innerjoin.org ---
> My system uses OpenRC.
Don't know whether OpenRC gives you a way of limiting the memory use (with
cgroups?). I only know the systemd unit files. Putting some sort of cap on the
memory use is sensible.
https://bugs.kde.org/show_bug.cgi?id=476479
--- Comment #4 from David Kredba ---
mdb_copy -n downsized it to 31 GiB.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=476479
--- Comment #3 from David Kredba ---
My system uses OpenRC.
I started the indexing on KF 5.110, during the compilation it was paused.
I am definitely not going to try to really use it (but I would like to!) if I
will be told that after each KF5/6
https://bugs.kde.org/show_bug.cgi?id=476479
tagwer...@innerjoin.org changed:
What|Removed |Added
CC||tagwer...@innerjoin.org
--- Comment
https://bugs.kde.org/show_bug.cgi?id=476479
--- Comment #1 from David Kredba ---
I am sorry, the complete backtrace follows:
Application: baloo_file (baloo_file), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6 __pthread_kill_implementation
12 matches
Mail list logo
