[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [nepomuk] [Bug 324307] Nepomukindexer segfaults then core dumps ad finitum using 100% CPU
From:       Simeon Bird <bladud () gmail ! com>
Date:       2013-08-31 17:45:50
Message-ID: bug-324307-17878-Rbs9ebbkip () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=324307

--- Comment #4 from Simeon Bird <bladud@gmail.com> ---
This page is useful in general:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

For bugs like this one the best thing you can do if to attach a copy of the
file nepomukindexer crashes on to the bug report. You can find this by looking
at the process list (press ctrl+esc). There will be a process with the command
"nepomukindexer FILENAME". Attach that filename to this report.

If you are using arch like the original reporter, there are no debug symbols,
so to get a useful backtrace/core dump you have to recompile using abs. To do
this, in /var/abs/extra/nepomuk-core/PKGBUILD, change:    
"-DCMAKE_BUILD_TYPE=Release \" to "-DCMAKE_BUILD_TYPE=Debug \" (note the
backslash!) and add a line with options=(!strip) near the top.

In your case, Sudhir, I think nepomuk has crashed somehow. Try disabling it in
systemsettings, hitting apply, and re-enabling it. If that doesn't work, try
removing your database (WARNING! this will delete your tags) with 

rm -R $HOME/.kde4/share/apps/nepomuk/repository/main/data/virtuosobackend

and follow the above instructions.

Also, helpful bug reports are really appreciated - they're the best way we have
to improve the software. If you can send me the file it crashes on, I can
probably fix this pretty quickly, so good luck!

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]