You shouldn't see this bug in 4.8.2 (and later) simply because the nepomuk plugin is not used anymore - so there is no mutithreaded nepomuk access anymore.
KAMD still saves some data into nepomuk, but not as much as before.
That is the reason I haven't closed this report - the multithreaded nepomuk access issue is still here, just kamd is not triggering it anymore.
In order to reproduce, kamd needs to be build with KACTIVITIES_BUILD_NEPOMUK_PLUGIN option activated (and the sqlite plugin needs to be disabled when starting kamd)
You shouldn't see this bug in 4.8.2 (and later) simply because the nepomuk plugin is not used anymore - so there is no mutithreaded nepomuk access anymore.
KAMD still saves some data into nepomuk, but not as much as before.
That is the reason I haven't closed this report - the multithreaded nepomuk access issue is still here, just kamd is not triggering it anymore.
In order to reproduce, kamd needs to be build with KACTIVITIES_ BUILD_NEPOMUK_ PLUGIN option activated (and the sqlite plugin needs to be disabled when starting kamd)