You can start the strigi service manually via: gdb --args nepomukservicestub nepomukstrigiservice
then type "run", wait for it to crash, then type "bt" and send the backtrace. It will most likely be a strigi bug, i.e. should be reported at strigi.sf.net. Cheers, Sebastian On 06/17/2010 08:26 PM, Sten Heinze wrote: > Hi, > > after copying some dirs into my home, the KDE strigi process started to crash > and stop. To verify I removed the dirs again, and strigi works fine. Then I > tried to start nepomuk and strigi from the commandline, to see errors. But I > don't know how to debug this further and get a crash backtrace and find the > file > causing this. So with the hope of some pointers on how to proceed I attach > the > commandline output from starting nepomuk and strigi. > > I am running Debian testing. nepomukserver --version prints Qt: 4.6.3 KDE: > 4.4.4 Nepomuk Server: 0.2. > > Thanks, > Sten > > PS. > I am not on the list, so please keep me CC:ed. > > > > _______________________________________________ > Nepomuk mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/nepomuk _______________________________________________ Nepomuk mailing list [email protected] https://mail.kde.org/mailman/listinfo/nepomuk
