Bug 250363 - nepomukservices segmentation fault
Summary: nepomukservices segmentation fault
Status: RESOLVED NOT A BUG
Alias: None
Product: nepomuk
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-06 15:23 UTC by fabio de francesco
Modified: 2011-09-28 09:25 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description fabio de francesco 2010-09-06 15:23:48 UTC 
Version:           unspecified (using KDE 4.5.0) 
OS:                Linux

In dmesg I have found a few errors related to the Nepomuk services:

nepomukservices[5484]: segfault at 7fd900000000 ip 00007fd92a9bc6db sp 00007fffddad0e10 error 4 in libsoprano.so.4.3.0[7fd92a96b000+ee000]
nepomukservices[5485] general protection ip:7f009b5946db sp:7fffeb207b40 error:0 in libsoprano.so.4.3.0[7f009b543000+ee000]
nepomukservices[5486] general protection ip:7f2328c666db sp:7fff3a036830 error:0 in libsoprano.so.4.3.0[7f2328c15000+ee000]
nepomukservices[5496]: segfault at 100000011 ip 00007f6e03b5f6e6 sp 00007fffff5c72e0 error 6 in libsoprano.so.4.3.0[7f6e03b0e000+ee000]

Furthermore the Nepomuk services are never started with a KDE new session and I have to start Strigi indexing from the System Settings. I need to check the option "Enable Strigi Desktop File Indexer" more than a few times before getting the message that Strigi is indexing files. At a first two or three attempts it returns messages saying it can't start indexing files due to an installation problem. 

Reproducible: Always

Steps to Reproduce:
restart kde session.

Actual Results:  
-1- Segfault messages in dmesg.
-2- Strigi indexing fails at starting.

Expected Results:  
-1- No segfaults
-2- Strigi indexing starts
Comment 1 Sebastian Trueg 2010-09-08 09:33:09 UTC 
I would need an actual crash backtrace in order to debug this.
Comment 2 fabio de francesco 2010-09-10 12:32:43 UTC 
(In reply to comment #1)
> I would need an actual crash backtrace in order to debug this.

How could I provide the actual crash backtrace? As I wrote those messages appear only in dmesg and they are not synchrounus with any particular action taken by me in working with Nepomuk.

Any idea?

Thanks,

fabio
Comment 3 Sebastian Trueg 2011-09-28 09:25:55 UTC 
Closing this bug as invalid. This is not correct but we are missing a backtrace and I am pretty sure it is a duplicate of one of the other crash reports and will be fixed. :)