Hello,
same for me. How can I reindex all my data?.
Regards.
qdbus-qt4 org.kde.nepomuk.services.nepomukfileindexer /nepomukfileindexer org.kde.nepomuk.FileIndexer.indexFolder path-to-folder 1 1
same for me. How can I reindex all my data?.
Regards.
]]>nepomukindexer dies and gets respawned. This causes a new process, systemd-coredump (eats 15MB of RAM), to be created. If you wait a while then systemd-journald will process something and the systemd-coredump will terminate, however the new nepomukindexer soon dies. Since nepomukindexer dies and respawns faster than systemd-journald can terminate the systemd-coredumps I end up with heaps of these 15MB processes sitting in the queue, hitting swap.
You can killall systemd-coredump since they are owned by your user once you see it start.
I can also confirm that the indexer only runs when the screen-locker is on
]]>nepomukindexer[13183]: segfault at 560 ip 00007f764b9cf6a6 sp 00007fffe7e8de90 error 4 in libQtGui.so.4.8.5[7f764b5da000+a5e000]
or
systemd-coredump[13187]: Process 13183 (nepomukindexer) dumped core.
Any ideas? Was it solved for the first ones posted?
Thanks
]]>