https://bugs.kde.org/show_bug.cgi?id=389848
Christoph Cullmann <cullm...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Latest Commit|https://github.com/LMDB/lmd |https://invent.kde.org/fram
|b/commit/1ffe472a080fcd3c7d |eworks/baloo/-/commit/15083
|ab6e352848703ad7adbe14 |afb9671ec79eb2dbee4ef41a925
| |56d154af
Resolution|--- |FIXED
--- Comment #191 from Christoph Cullmann <cullm...@kde.org> ---
Git commit 15083afb9671ec79eb2dbee4ef41a92556d154af by Christoph Cullmann.
Committed on 07/04/2024 at 14:22.
Pushed by cullmann into branch 'master'.
Don't kill the lock file, can lead to random corruption
If a process that writes the database is still running,
like an existing baloo_file_extractor, and one starts a new instance
of baloo_file, that one will remove the lock and now
two writers will use the same database without proper locking.
M +0 -4 src/file/main.cpp
https://invent.kde.org/frameworks/baloo/-/commit/15083afb9671ec79eb2dbee4ef41a92556d154af
--
You are receiving this mail because:
You are watching all bug changes.
