Bug 815616 - Nepomuk terminated with Signal 11
Summary: Nepomuk terminated with Signal 11
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: nepomukcontroller
Version: 16
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Jaroslav Reznik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-24 04:23 UTC by Ryan
Modified: 2012-06-19 10:11 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-19 10:11:26 UTC
Type: Bug


Attachments (Terms of Use)

Description Ryan 2012-04-24 04:23:12 UTC
Description of problem:

Shows up at boot in the bug reporting tool when trying to report throws error that backtrace is unuseable...

Version-Release number of selected component (if applicable):

kde-runtime 4.8.2

How reproducible:

happens every boot up

Steps to Reproduce:
1. load fedora
2. log in as local user
3. bug report tool shows up with error
  
Actual results:

indexer doesn't load

Expected results:

indexer to load without error

Comment 1 Ryan 2012-04-24 11:57:10 UTC
dunno if it helps, but found the following line in /var/log/messages:

Apr 24 00:44:59 <hostname> kernel: [16858.347538] nepomukservices[3258]: segfault at 0 ip           (null) sp 00007fffc970be28 error 14 in nepomukservicestub[400000+7000]

Comment 2 Rex Dieter 2012-04-24 12:26:33 UTC
without a backtrace, I'm only speculating, but... this usually indicates a corrupted nepomuk database, remove/rename/backup items matching:
~/.kde/share/apps/nepomuk/
~/.kde/share/config/nepomuk*

and see if problems persist.

Comment 3 Ryan 2012-06-19 10:11:26 UTC
Thanks Rex, I've removed the files as indicated and the issue appears to have been rectified.


Note You need to log in before you can comment on or make changes to this bug.