https://bugs.kde.org/show_bug.cgi?id=437176
Peter Wu <pe...@lekensteyn.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pe...@lekensteyn.nl
--- Comment #7 from Peter Wu <pe...@lekensteyn.nl> ---
Setting a breakpoint on KIO::buildErrorString was unfortunately not that
helpful, it just pointed out that a error came from an external connection. Via
KIO::ConnectionPrivate::commandReceived it became clear that a
task.cmd=KIO::MSG_ERROR was received.
With "KDE_FORK_SLAVES=1" set, there was some more helpful output:
$ KDE_FORK_SLAVES=1 strace -ftto st.txt -s2000 okular
kf.baloo.engine: PostingDB::open MDB_NOTFOUND: No matching key/data pair
found
kf.baloo.engine: PositionDB::open MDB_NOTFOUND: No matching key/data pair
found
kf.baloo.engine: DocumentDB::open docterms MDB_NOTFOUND: No matching
key/data pair found
kf.baloo.engine: DocumentDB::open docfilenameterms MDB_NOTFOUND: No
matching key/data pair found
kf.baloo.engine: DocumentDB::open docxatrrterms MDB_NOTFOUND: No matching
key/data pair found
kf.baloo.engine: IdTreeDB::open MDB_NOTFOUND: No matching key/data pair
found
kf.baloo.engine: IdFilenameDB::open MDB_NOTFOUND: No matching key/data pair
found
kf.baloo.engine: DocumentTimeDB::open MDB_NOTFOUND: No matching key/data
pair found
kf.baloo.engine: DocumentDataDB::open MDB_NOTFOUND: No matching key/data
pair found
kf.baloo.engine: DocumentIdDB::open indexingleveldb MDB_NOTFOUND: No
matching key/data pair found
kf.baloo.engine: DocumentIdDB::open failediddb MDB_NOTFOUND: No matching
key/data pair found
kf.baloo.engine: MTimeDB::open MDB_NOTFOUND: No matching key/data pair
found
kf.baloo.engine: dbis is invalid
kf.kio.slaves.tags: tag fetch failed: "Failed to open the database"
kf.kio.slaves.tags: "tags:/" list() invalid url
kf.kio.core: "Could not enter folder tags:/."
On my system, I have baloo disabled. I can confirm that after "balooctl purge",
the error went away.
Environment:
Arch Linux
baloo 5.84.0-1
kio 5.84.0-2
--
You are receiving this mail because:
You are watching all bug changes.
