Bug 298700

Summary:	Kmail says in composer that I don't have the Semantic Desktop enabled even though I do
Product:	[Applications] kmail2	Reporter:	Ralph <R.Clark.01>
Component:	composer	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	montel
Priority:	NOR
Version:	4.8.0
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
URL:	http://i43.tinypic.com/2cpqhrd.jpg
Latest Commit:		Version Fixed In:
Attachments:	Screenshot of system settings -> desktop search with "details" clicked

Description Ralph 2012-04-23 21:35:59 UTC

As title. In composer if I click on configure I get the screenshot that you can see above. I have Semantic Desktop enabled but for reason it thinks I don't.

Reproducible: Always

Steps to Reproduce:
1. Load Kmail
2. Click on compose
3. Click on configure
Actual Results:  
Obtained the screenshots above

Expected Results:  
It shouldn't give this warning as I apparently _do_ have Semantic Desktop enabled.

I can't access my address book because of this bug as well.

Comment 1 Laurent Montel 2012-04-24 07:03:31 UTC

which screenshot ?

Comment 2 Ralph 2012-04-24 08:27:58 UTC

The screenshot is in the "URL" field of this bug report.

Comment 3 Christophe Marin 2012-04-24 08:55:32 UTC

For the next time, please attach the screenshot directly in the bug report. This way, it won't get lost

Please paste the output of `ps x |grep nepomuk` please.

Could be that one of the Nepomuk process doesn't start (or crashes in the background)

Comment 4 Ralph 2012-04-24 21:46:40 UTC

 ps x | grep nepomuk
 3063 ?        Sl     0:00 kdeinit4: nepomukserver [kdeinit] 
 3074 ?        S      0:00 /usr/bin/nepomukcontroller -session 10dcce636b000132683059500000028850010_1335228215_94737
 3125 ?        S      0:00 /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder
 3702 pts/1    D+     0:00 grep --colour=auto nepomuk

Comment 5 Laurent Montel 2012-04-25 06:30:19 UTC

for me:

 3984 ?        Sl     0:00 kdeinit4: nepomukserver [kdeinit]                   
 3986 ?        SNl    0:16 /opt/kde4/bin/nepomukservicestub nepomukstorage
 3990 ?        S      0:00 /opt/kde4/bin/nepomukcontroller -session 10d0d4d472000132274332600000263900009_1335301009_57023
 4155 ?        S      0:01 /opt/kde4/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder
 4156 ?        S      0:00 /opt/kde4/bin/akonadi_nepomuktag_resource --identifier akonadi_nepomuktag_resource
 4712 ?        SN     0:00 /opt/kde4/bin/nepomukservicestub nepomukbackupsync
 4716 ?        SNl    0:05 /opt/kde4/bin/nepomukservicestub nepomukfilewatch
 4720 ?        SN     0:00 /opt/kde4/bin/nepomukservicestub nepomukqueryservice
 4721 ?        SNl    0:02 /opt/kde4/bin/nepomukservicestub nepomukfileindexer
 5324 ?        RN     0:00 /opt/kde4/bin/nepomukindexer /home/laurent/....
 5326 pts/4    S+     0:00 grep --color=auto nepomuk*

Comment 6 Christophe Marin 2012-04-25 19:44:26 UTC

Ralph, your output clearly indicates nepomuk is not started.

try running 'nepomukserver'

Comment 7 Ralph 2012-04-25 22:07:56 UTC

$ nepomukserver
Nepomuk server already running.
$ ps x | grep nepomuk
 2952 ?        Sl     0:00 kdeinit4: nepomukserver [kdeinit] 
 2962 ?        S      0:00 /usr/bin/nepomukcontroller -session 10dcce636b000132683059500000028850010_1335316567_343078
 3053 ?        S      0:00 /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder
 3479 pts/2    D+     0:00 grep --colour=auto nepomuk

It thinks that Nepomuk server is still running. What does the first line of my original posted output mean if not that the server is already running?

Comment 8 Christophe Marin 2012-04-30 09:17:59 UTC

means the nepomukserver process is running but not its services (that makes it doing nothing and being unusable)

attach a screenshot of systemsettings / Desktop Search please

Comment 9 Ralph 2012-04-30 20:34:25 UTC

Created attachment 70782 [details]
Screenshot of system settings -> desktop search with "details" clicked

Comment 10 Christophe Marin 2012-05-22 22:58:41 UTC

Thanks. Merging with 294320

*** This bug has been marked as a duplicate of bug 294320 ***