https://bugs.kde.org/show_bug.cgi?id=468337
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagwer...@innerjoin.org
--- Comment #1 from tagwer...@innerjoin.org ---
(In reply to Elias Probst from comment #0)
> 1. Corrupt your DB (procedure unknown)
Chuckle :-)
The most recent option for doing this related to non-printable characters
(things like \000 and \001) in the file. See Bug 464226 and
https://invent.kde.org/frameworks/baloo/-/merge_requests/87
This, at least, should be sorted in Frameworks 5.105
> ... let the user know ... the DB got corrupted ...
There's a database consistency check script (by Igor Poboiko) here
https://invent.kde.org/frameworks/baloo/uploads/bdc9f5f17fc96490b7bd4a22ac664843/baloo-checkdb.py
that he refers to in:
https://invent.kde.org/frameworks/baloo/-/merge_requests/87#note_535270
That might be worth a try. Heads up about the need to load the whole database
into memory
If you've got a corruption, probably your only option is to purge and reindex.
> SOFTWARE/OS VERSIONS
> Linux/KDE Plasma: NixOS/nixpkgs unstable 19cf008bb1
That may be an interesting journey... I got there with:
environment.systemPackages = with pkgs; [
(python3.withPackages(ps: with ps; [ lmdb ]))
];
and then
$ python3 baloo-checkdb.py
But whether this works in a general case...
--
You are receiving this mail because:
You are watching all bug changes.
